this wait type can also occur when an AlwaysOn DDL statement or Windows Server Failover Clustering command is waiting for exclusive read/write access to the configuration of an availability group
Waitopedia is a comprehensive resource of information about SQL Server waits.
The description shown below is the top answer as voted by the Spotlight community.
The charts are based on 2.1 TB of data collected from 4207 instances uploaded by 323 Spotlight users over an 8 week period.
|
this wait type can also occur when an AlwaysOn DDL statement or Windows Server Failover Clustering command is waiting for exclusive read/write access to the configuration of an availability group |
|
|
Occurs when an AlwaysOn DDL statement or Windows Server Failover Clustering command is waiting for exclusive read/write access to the configuration of an availability group. Information from Microsoft® |
|
This wait never occurs for most instances
For each of 4207 instances, we ranked HADR_AG_MUTEX on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.
For 78 % of hours with this wait, average wait time is less than 0.62 ms
For each instance, we found all the recent hours when it had a HADR_AG_MUTEX wait. We found the average latency for each of those hours.
409 instances contributed data to this chart