Unsolved Server 2016 Hyper-V cluster node isolation?

---

If I have a three node 2016 Hyper-V cluster, what settings would I modify if I wanted VMs to be moved off of an isolated node automatically after one minute? I am thinking I would make the following chagnes:

ResiliencyLevel: <Leave default value>
(Get-Cluster).ResiliencyLevel = 2

ResiliencyPeriod:
(Get-Cluster).ResiliencyDefaultPeriod = 60

I am pretty confident with the ResiliencyPeriod, but I am not sure I fully understand the ResiliencyLevel setting. Why would I leave this in the default state vs changing it to "1"?

Web description:

ResiliencyLevel
1 – Allow the node to be in Isolated
state only if the node gave a notification and it went away for known reason, otherwise fail immediately. Known reasons include Cluster Service crash or Asymmetric Connectivity between nodes.

2- Always let a node go to an Isolated state and give it time before taking over ownership of the VMs.

Adam,

I hope all is well. Take a look at the following:

https://blogs.msdn.microsoft.com/clustering/2015/06/03/virtual-machine-compute-resiliency-in-windows-server-2016/

Down towards the bottom is the grid that explains the settings, as you have already noted above in your question. The real trick with these settings is to understand the context that will surround the move to an isolated state in the real world when the cluster is experiencing transient failure scenarios. Known reasons are defined as:

Node disconnected: The cluster service attempts to connect to all active nodes. The disconnected (Isolated) node cannot talk to any node in an active cluster membership.

Cluster Service crash: The Cluster Service on a node is down. The node is not communicating with any other node.

Asymmetric disconnect: The Cluster Service is attempting to connect to all active nodes. The isolated node can talk to at least one node in active cluster membership.

So basically what we have is a situation where if you leave the default setting of 2, then you are setting a broad net that will trigger for ANY reason, known or not.

If on the other hand, you change the setting to 1, you are casting a constrained, and narrowly defined net that will trigger ONLY IF a known condition is occurring.

Hope that helps to clarify.

Cheers,

Adam