Description

For databases utilizing Availability Groups with a listener configured. This wait will accumulate when a listener experiences a status transition (stop, started or failover) through the Windows Cluster Service or by an internal Availability Group command. This wait type is uncommon and should not be high

Resolved by

DBAs

Suggested solutions

1. Check the SQL Server error log for more information
2. Examine Windows Failover Clustering logs to determine the cause of listener status changes
3. Examine wait statistics on the instance for other Availability Group issues. Investigate accordingly

Additional research

Availability Group Listeners, Client Connectivity, and Application Failover
Create or Configure an Availability Group Listener
AlwaysOn Availability Groups Troubleshooting and Monitoring Guide

⇐ Back to index