03.14
And the final patch (there’s more so you should check out the Failover Clustering patching wiki) for clustering. I’m only listing the Hyper-V related ones.
“Consider the following scenario:
- You set a preferred node in a Windows Server 2008 R2-based failover cluster.
- You set the failback policy of this node to Allow Failback, select the Failback between option, and then set a failback time interval.
- You move a cluster resource group from the preferred node to another node.
- You try to shut down the preferred node.
In this scenario, the shutdown operation stops responding at the Shutting down Cluster Service phase. It takes about 30 minutes for the node to shut down.
This issue occurs because the Cluster service tries to fail back the resource group every 15 minutes when the following conditions are true:
- A failback time interval is set.
- The time that is used to shut down the node is longer than the failback time interval.
When the failback process fails, the thread that performs the operation sleeps for 15 minutes. If you try to shut down the Cluster service on this node, the operation waits until the cluster shutdown times out”.
A supported hotfix is available from Microsoft.
Copyright Warning
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.
Related posts:
- KB2575625 – W2008 R2 Cluster Starts Failover After 80 Seconds When You Shutdown Active Node
- KB2549472 – W2008 R2 Cluster Node Cannot Rejoin Cluster After Node is Restarted Or Removed From Cluster
- KB2727972–W2008 R2 Cluster Node Crashes When You Restart A Node
- KB2710487 – Error 1359 & Cluster Service Stops In W2008 or W2008 R2 Failover Cluster
