Microsoft has released a hotfix for when the cluster service initiates a failover after a delay of about 80 seconds when you shutdown the active node in Windows Server 2008 R2.
Consider the following scenario:
- You configure a failover cluster on some computers that are running Windows Server 2008 R2.
- You add a crossover cable between two nodes of the cluster.
- You shutdown the active node of the cluster.
In this scenario, the Cluster service initiates a failover after a delay of about 80 seconds.
Note The Cluster service usually initiates the failover within 5 seconds.
This issue occurs because the Cluster service incorrectly waits for Global Update Manager (GUM) updates.
A hotfix has been released to fix this issue.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
- KB2549472 – W2008 R2 Cluster Node Cannot Rejoin Cluster After Node is Restarted Or Removed From Cluster
- KB2710487 – Error 1359 & Cluster Service Stops In W2008 or W2008 R2 Failover Cluster
- KB2727972–W2008 R2 Cluster Node Crashes When You Restart A Node
- KB2769588 – An Update That Adds 4-Node Failover Cluster Deployment Support In OEM WS2012 OOBE
- KB2750149 Causes Failover Cluster Manager To Crash On Windows Server 2012