Description

For databases utilizing Availability Groups. This wait accumulates when the log capture mechanism (used to send/receive changes between primary and secondaries) is waiting for new log records to become available. This is a common wait, high values can often be ignored. However, if values are excessive or secondary replicas are frequently losing synchronized status then investigation is required

Resolved by

DBAs

Suggested solutions

1. Examine Availability Group performance monitor counters
2. Check the SQL Server error log for more information
3. Examine wait statistics on the instance for other Availability Group issues. Investigate accordingly

Additional research

AlwaysOn Availability Groups Troubleshooting and Monitoring Guide

⇐ Back to index