Either the internal AlwaysOn system or the WSFC cluster will request that listeners are started or stopped. The processing of this request is always asynchronous, and there is a mechanism to remove redundant requests. There are also moments that this process is suspended because of configuration changes. All waits related with this listener synchronization mechanism use this wait type. Internal use only. Information from Microsoft®
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.
HADR_TDS_LISTENER_SYNC
Category: Idle
SQL Server versions: 2012, 2014, 2016, 2017
This is an idle wait and so it can be safely ignored.
What is HADR_TDS_LISTENER_SYNC?
1 Answer
|
|
answered 3348 days ago
Spotlight Essentials
|
|
|
This wait never occurs for most instances
For each of 4207 instances, we ranked HADR_TDS_LISTENER_SYNC on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.
Prevalence of HADR_TDS_LISTENER_SYNC across the Spotlight Population
For 100 % of hours with this wait, average wait time is above 1 ms
For each instance, we found all the recent hours when it had a HADR_TDS_LISTENER_SYNC wait. We found the average latency for each of those hours.
1 instance contributed data to this chart