Windows cluster heartbeat detection threshold optimization

View the current cluster's property information through the cmd command Cluster.exe/prop, where the heartbeat threshold related properties:

• Samesubnetdelay: Signal frequency of nodes in the same subnet
• Samesubnetthreshold: Threshold of latency for nodes in the same subnet
• Crosssubnetdelay: Detection signal frequency of nodes in different subnets
• Crosssubnetthreshold: Thresholds for the latency of nodes in different subnets

Samesubnetdelay The default is to perform a Windows cluster heartbeat test every 1 seconds, Samesubnetthreshold represents a Windows cluster that allows a maximum heartbeat failure of 5, which could cause a cluster failover.

The range of heartbeat adjustments allowed is as follows: The maximum is allowed to be detected every 2 seconds, and 10 consecutive failures are failures.

Property	Default value	Allowable range values
Samesubnetdelay	1000ms	250ms~2000ms
Samesubnetthreshold	5	3~10
Crosssubnetdelay	1000ms	250ms~2000ms
Crosssubnetthreshold	5	3~10

To modify with the cmd command:

Cluster.exe/prop samesubnetdelay=2000

Cluster.exe/prop samesubnetthreshold=10

Cluster.exe/prop crosssubnetdelay=2000

Cluster.exe/prop Crosssubnetthreshold =10

View Results Cluster.exe/prop

Heartbeat detection Instructions

The simple understanding of heartbeat detection is that NODE1 sends a connection sequence number to Node2,node2 response to the same sequence number, Node1 sends an identical serial number to Node2 again, and Node2 responds to the same serial number again. Node1 will determine that this heartbeat sequence is complete and start another sequence detection, if the heartbeat sequence is deleted or not received in time during this detection, it will indicate missed this heartbeat, the default process five consecutive heartbeat sequence is missed, this node is considered inactive.

By modifying the thresholds, you can resolve a certain degree of network latency, but it does not solve the problem at all, so keep in mind that changes to the delay or threshold settings are not considered a troubleshooting technique. For heartbeat detection, IPV6 is used by default because it is a faster protocol than IPV4, and if IPV6 is disabled, it will use IPV4. Failover clusters do not mix and match IPv6 and IPV4. cannot be used at the same time.

Windows cluster heartbeat detection threshold optimization