Why can lock contention exhaust CPU if threads are waiting?
Waiting may consume CPU through spinning, repeated retries, scheduler activity or cache-coherence traffic, depending on the implementation. Even blocking waits add scheduling and wake-up work. The report confirms CPU and memory exhaustion but does not specify which of these mechanisms dominated.
Answered in
Inside the Microsoft 365 Gateway Failure: Lock Contention to CascadeA technical reconstruction of how a gateway lock defect, shifted load and shrinking capacity can turn queued requests into fleet-wide failure.
Read the full analysisOther questions this article answers
More distributed systems questions
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Distributed Systems beat.