| ▲ | mminer237 a day ago |
| Newest update says that wasn't the issue after all. They say relatively small loads are actually causing servers to become unresponsive and have to be restarted. They still don't know why this "core process" is maxing out the processor for no reason. |
|
| ▲ | SoftTalker a day ago | parent | next [-] |
| I'd start with "what has changed" but surely they've looked at that. |
| |
| ▲ | NetMageSCW 5 hours ago | parent | next [-] | | They did look at recent changes but none seemed to be related, but it turned out recent network changes triggered a failure mode in a much older network change. Dependent or cascading issues remain hard to diagnose or find. | |
| ▲ | jamesfinlayson 20 hours ago | parent | prev [-] | | Could be something adjacent - the last time I majorly blew up a release was because something had changed (which was fine) but it caused a list of items to be broken over two pages, but only in prod. Me and a team mate were scratching our heads for the longest time because "what had changed" was quite mundane itself. | | |
| ▲ | sire-vc 13 hours ago | parent [-] | | The classic 'database is smaller in testing than in prod' problem which is responsible for some outages IME.
Often the 'query was not optimised but that didn't show until prod' one. |
|
|
|
| ▲ | waz0wski 21 hours ago | parent | prev [-] |
| There was an article posted by a former MS / Azure person earlier this year that described the dumpster fire of node management and their cloud control plane https://isolveproblems.substack.com/p/how-microsoft-vaporize... HN discussion - https://news.ycombinator.com/item?id=47616242 |
| |
