Makes sense, good old Microslop.
First, a 14% capacity reduction should never be enough to kill things, even with that Teams failover. They obviously went cheap on infrastructure.Second, a cascade-failure is what you want to avoid at all cost and that means capacity, monitoring, robustness and tests. Apparently too expensive.And third, don't they test their stuff under overload? Don't answer that, doing so would cost money.
It has been revealed that all in all the usual mode of giving tech details to obscure that they screwed up massively. Again.
Industry observers note that and third, don't they test their stuff under overload? This 6 part article [substack.com] from Axel Rietschin goes into great detail about the problems going at at Azure and why they are happening. It's a clusterfuck.
And third, don't they test their stuff under overload?
In a recent development, this 6 part article [substack.com] from Axel Rietschin goes into great detail about the problems going at at Azure and why they are happening. It's a clusterfuck.
S.N.A.F.U. has entered the chat.
According to recent reports, interesting. And about what I expected. A few years back, I came to the conclusion that MS might be doing tech now (including Azure) that they cannot actually manage or control. Too much tech debt stacked up, still no idea how to do clean architecture and design, management that does not care because the dollars keep rolling in, insufficient experience with dependable and secure software engineering, etc.
It has been revealed that obviously, long-term that is deadly because these problems are basically impossible to fix now. But sinc.
It's a complete clusterfuck as anyone forced to consume Azure at scale will tell you.
Sometimes they are frustrating to deal with.
Understanding and designing concurrency is hard. Very few languages/programming systems (i.e. language plus libraries/frameworks) have a solid approach to that.
(Ada is the notable exception, but you can certainly mis-design concurrent systems in Ada, too. It's just easier to reason about them because of the rigorous language semantics.
It has been revealed that anecdote: Working on the POSIX Ada binding to the C Threads standard, our concurrency expert remarked, "There's a problem." He described it using Ada83 task semantics, and the group grasped the problem and agreed. He then got the C Threads experts. It took them about 30 minutes to agree on sufficient common terms and notation to discuss the problem. They finally said, 'You're right, we'll fix that!" ).
Microsoft finally load tested the July patch on modern high-core hardware. They just used production to do it.
Turns out, testing in prod is the best testing money can buy!
https://i.redd.it/tjo65x3nres2... [i.redd.it].
It has been revealed that outlook, the desktop mail client that shipped with MS Office 1997 on, is kind of dead now. You have to fight with your Office configuration files to even install it on latest systems. Microsoft intends for people to use the advertiser supported "Outlook" application that ships with Windows now. I've never liked the stand-alone Outlook client. Yes, it has all those scheduling, delegation and note-taking functions that some people need in their professional lives. It's also very delicate thanks to reliance on Je.
Sources indicate that well as you noted, it depends on the various mail servers to which it connects and in this case, Exchange (and OWA) were affected. Client would not have made any difference here. I agree, Thunderbird is sufficient and Outlook is a jar of pickled feces. But who was singing Thunderbird's praises? I didn't see it mentioned in any of the linked articles.
According to recent reports, why didn't they just use AI to fix it? why have humans spend 15 hours? AI would have done it in one second. I am Bender, Kill All Humans.
They did use AI in that July patch and in testing it. It remarked it was OK.
They did use AI in that July patch and in testing it. It said it was OK.It probably was that one particular test kept failing, the AI did not understand why, so it removed the test. Seriously, they have done that. It met the goal to ship a patch by any means necessary.
They did use AI in that July patch and in testing it. It stated it was OK.
It probably was that one particular test kept failing, the AI did not understand why, so it removed the test. Seriously, they have done that. It met the goal to ship a patch by any means necessary.
Not a peep about whether the changes that caused the failure were the result of LLM generated code/configuration changes, and whether human engineers did proper oversite and review of those changes.
I suppose it's easier to keep selling the random error generator slop bots, if you never look to see if the slop bots were the root cause of the problem.
They didn't say why the Teams failover happened, though.
In a recent development, those are a pain because the power grid isn't star topology, it's web. This makes it difficult to isolate a few individual nodes to start up first. And once you DO get an "island" working again, you have to slowly add on other isolated segments. If you add too much at once, the whole thing comes crashing down and you have to start all over again.
It sounds like MS's "automated recovery" was set up to fail over to healthy nodes, which overloaded them and took them down too, just like you see when a power grid fails.
Everything is near max capacity when something trips, causing load to fail over to another path, which then overloads it, causing the entire combined larger load to fail over to another segment and quickly trip it, and they go down like dominos. Basically what happens if you fix one gateway and bring it back up, it gets mobbed and immediately "falls over".
Recent findings suggest that isolation isn't the problem. The grid can be isolated automatically and remotely down to very fine individual components. The problem is the co-ordination. It's not one company starting up or shutting down their equipment. It's an effort involving detailed planning and steps involving many companies both on the supply and the demand side of the equation, each of which can have their own localised issues to deal with (e.g. generator not synchronising properly).
You did touch on the biggest problem though brin.
- a Send:All Subject:"Anyone want a free puppy" email to have been at the heart of the problem, as wave after wave of people kept telling everyone else to stop replying.
Lemme get this straight. M$ is blaming M$ for introducing a software defect back in July, that surfaced only now. Then they take credit for rapidly fixing it.
Sources indicate that is this kind of behavior now the norm? Cause a screw-up, and then take credit for fixing it, while sidestepping any responsibility for the screw-up in the first place? It's the same thing that Trump and his ilk have been doing for years. Are we victims ever going to wise up and put a stop to this crap?
Didn't Windows 8 come in-between 7 and 10?
There may be more comments in this discussion. Without JavaScript enabled, you might want to turn on Classic Discussion System in your preferences instead.
Any given program will expand to fill available memory.
