We have an availability group

Replica-01 (Sync on-premise) PRIMARY
Replica-02 (Sync on-premise) SECONDARY
Replica-03 (Async Azure VM) SECONDARY

Replica-01 is sometimes having lease time out and availability group is entering RESOLVING state for short period of time, effectively an outage on production for 30-60 sec
Looking at Cluster log, we see below:

Lease renewal failed because the existing lease is no longer valid. The lease is expired

Availability Group lease is no longer valid. Resource Alive result 0.

Cluster log reports that performance counters collected before lease time out showed 100% CPU utilization

Some server-wide event is happening that is causing Availability Group / Primary replica loosing heartbeat with Windows Failover Cluster, but what exactly ?

How can I diagnose and resolve those type of problem ?

  • 'Availability Dashboad' is the best way to track the 'AlwayaOn availability Group'. Which comes by default with SSMS tools. – Md Haidar Ali Khan Dec 11 '17 at 13:01
  • It would be wise to add output of select @@version in your question – Shanky Dec 11 '17 at 13:23
  • 1
    You need to find out what process is exhausting CPU resources. Set up perfmon logging with CPU utilization (% User Time) for <All Instances> selected, then review it after the fact to see what process is using high CPU. – Tony Hinkle Dec 11 '17 at 14:15
  • Have you reviewed this: blogs.msdn.microsoft.com/alwaysonpro/2016/02/23/… – Shawn Melton Dec 11 '17 at 17:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.