If lag between primary and secondary is huge, then can it cause persistent blocking on app sessions? Coz recently we had an issue where blocking sessions were having wait type as HADR_SYNC_COMMIT and there was lag for one of the DB in AG.

So we failover to Secondary even though the lag was pretty high. After DB coming online on new Primary, issue got resolved.

But today the issue happened again. Can you please help.

  • Yes, that could cause commits to be very slow and result in locks being held much longer. Without more information there's not much we can do to help. In general you have to start looking for evidence of anything with the OS, hardware, network, VM host, and SQL Server that might be causing poor I/O or network performance. Commented Nov 7, 2019 at 10:13

1 Answer 1


As addition to Tony's comment this MSDN post can help you with performance counters and latency factors.

Also, verify one of the known issue (lag) "redo blocking on secondary due to schema changes on primary", you can verify that via built-in Xevent's session or follow these steps for validation of redo blocking and quick fix.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.