May 15, 2018 at 5:48 pm
Hi everyone,
I am taking over a SQL AlwaysOn Availability Group Clustering and there is a cluster node in a remote location who is acting as a asynchronous replica. The latency between this node of the rest of the cluster is about 65ms. I receive alerts from time to time that the DR cluster node was removed from the active failover cluster membership and it is probably due to latency.
I see the following errors:
Cluster has missed two consecutive heartbeats for the local endpoint 10.180.XXX.XXX:~3343~ connected to remote endpoint 10.182.XXX.XXX:~3343~.
Cluster has lost the UDP connection from local endpoint 10.180.XXX.XXX:~3343~ connected to remote endpoint 10.182.XXX.XXX:~3343~.
Cluster node 'DR' was removed from the active failover cluster membership.
I was wondering if it a common scenario in a DR case and how other administrators handle it ? Is it possible to increase the level of tolerance for that particular node ?
Thank you
May 15, 2018 at 6:39 pm
I found this article and helped me to understand https://blogs.msdn.microsoft.com/clustering/2012/11/21/tuning-failover-cluster-network-thresholds/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply