Error while switching availability group

Question

Hi.
I have two servers with sql server that run in the availability group. Worked properly for a long time, failover was changing the availability groups correctly.
when changing from primary to secondary server with the use of failover, the availability group which was secondary became primary and primary went into resolving state.
during the change, the event log logged me in the following entries:

Always On: The local replica of availability group 'GroupName' is preparing to transition to the resolving role. This is an informational message only. No user action is required.

The availability group 'GroupName' is being asked to stop the lease renewal because the availability group is going offline. This is an informational message only. No user action is required.

The state of the local availability replica in availability group 'GroupName' has changed from 'PRIMARY_NORMAL' to 'RESOLVING_NORMAL'. The state changed because the availability group is going offline. The replica is going offline because the associated availability group has been deleted, or the user has taken the associated availability group offline in Windows Server Failover Clustering (WSFC) management console, or the availability group is failing over to another SQL Server instance. For more information, see the SQL Server error log or cluster log. If this is a Windows Server Failover Clustering (WSFC) availability group, you can also see the WSFC management console.

Always On Availability Groups connection with secondary database terminated for primary database 'DataBaseName' on the availability replica 'WIN-XXXXXXX' with Replica ID: {XXXXX-XXXX-XXXX-XXXX-XXXXXXXX}. This is an informational message only. No user action is required.

The availability group database "DataBaseName" is changing roles from "PRIMARY" to "RESOLVING" because the mirroring session or availability group failed over due to role synchronization. This is an informational message only. No user action is required.

Remote harden of transaction 'TRUNCATE TABLE' (ID 0x000000014e4b95d6 0000:0000854d) started at Nov 26 2021 8:00AM in database 'DatabaseName' at LSN (104:25864:3) failed.

where there may be a problem, since the failover was working normally before??

Answer 1

Hi @Eryk17 ,

Using the Failover Cluster Manager to check the status of the Windows Cluster site, the first thing to verify is the cluster service, and if it's not running, start the service from that console.

When your availability group replica transitions to RESOLVING, this is effectively an outage in your production environment. This blog may be able to help you diagnose the problem

100%CPU utilization may cause Lease Timeout---temporarily adjust the availability group lease timeout property, increase LeaseTimeout value to make the AG remaining healthy

The lease may also expire due to a shortage of resource on the machine, likely to be relevant to I/O, if there is a lot of IO stalled messages, you need to consider storage performance

-------------

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.