Hi,
I found many times today, if there are two large databases are in recovery status(trying to catch up in availability group), the other databases needs recovery will be waiting.
The full story is I am fixing a broken availability group node, initially one large database is doing recovery, I fixed several other small databases(remove from ag, apply log backups and add it back in AG), then I started another large database, so in total there are two large databases doing recovery, I tried to started the third one "alter database db3 set hadr off" which is a small database, and it just hang there, it is suspended due to wait type hadr_ar_critical_section_entry:
"
Occurs when an Always On DDL statement or Windows Server Failover Clustering command is waiting for exclusive read/write access to the
runtime state of the local replica of the associated availability group.
Applies
to: SQL Server 2012 through SQL Server 2016.
"
I am not sure how the logic works in the background, can anyone shed some lights? thanks!
Here are the server/version details:
Microsoft SQL Server 2014 (SP2) (KB3171021) - 12.0.5000.0 (X64)
50GB memory and 12 cores assigned to this instance.