![]() ![]() As a result of this, latency for long running asynchronous operations (such as outgoing database and web requests) increased, leading to timeouts. This was caused by high-volume, short-held lock contention on the request serving path, which triggered a significant increase in spin-waits against these locks, driving up CPU load and preventing threads from picking up asynchronous background work. This incident was the result of a positive feedback loop leading to saturation on the ARM web API tier. Additionally, Azure services that leverage the ARM API as part of their own internal workflows, and customers of these services, may have experienced issues managing Azure resources located in West Europe as a result. This principally affected customers and workloads in geographic proximity to our West Europe region, while customers geographically located elsewhere would not have been impacted – with limited exceptions for VPN users and those on managed corporate networks. This caused up to 50% of customer requests to this region to fail (approximately 3% of global requests at the time). The primary source of impact was limited to ARM API calls being processed in our West Europe region. This impacted users of Azure CLI, Azure PowerShell, the Azure portal, as well as Azure services which depend upon ARM for their internal resource management operations.
0 Comments
Leave a Reply. |