![]() The availability group database “MyDatabase” is changing roles from “PRIMARY” to “RESOLVING” because the mirroring session or availability group failed over due to role synchronization. ![]() My first stop was the SQL Server error log on the primary replica, where this message was prominently displayed:Īlways On: The local replica of availability group ‘agMyDatabaseProd’ is preparing to transition to the resolving role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. We take downtime very seriously, so I started looking into the root cause. This resulted in 15 seconds of downtime for the application. Then, 15 seconds later, both servers returned to their previous statuses (so no failover occurred). I received an alert that both the primary and secondary replicas went into the “RESOLVING” state. One evening, the File Share Witness was taken down for maintenance. ![]() I’ve got a two-node synchronous availability group, with a File Share Witness as the third quorum vote. Specifically as those settings relate to availability groups, and how they can affect the reliability of the AG. I’m going to go a little outside my comfort zone and talk about Windows Server Failover Clustering (WSFC) settings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |