There are 2 ways of controlling the behavior of Node Fairness on a Hyper-V 2016 Failover Cluster, using Failover Cluster Manager and of course by PowerShell! In this blog post, we will go through the configuration of Node Fairness using PowerShell.
This is a 2 step configuration process.
First, we need to configure the level of aggressiveness of cluster based on the monitored heuristics which are CPU and Memory.
#Configuring Agressiveness of Balancing (Get-Cluster).AutoBalancerLevel = <value>
|1 (default)||Low||Move when host is more than 80% loaded|
|2||Medium||Move when host is more than 70% loaded|
|3||High||Move when host is more than 60% loaded|
Secondly, we need to configure the VM Load Balancing behavior of the cluster.
#Configure VM Load Balancing (Get-Cluster).AutoBalancerMode = <value>
|1||Load balance on node join|
|2 (default)||Load balance on node join and every 30 minutes|
The default values are the following:
- Auto Balancer Level: Move when host is more than 80% loaded (Value 1).
- Auto Balancer Mode: Load balance on node join and every 30 minutes (Value 2).
And this is how the configuration looks like in the Failover Cluster Manager.
More posts on Hyper-V 2016:
- Node fairness on Hyper-V 2016, VM Load Balancing for the SMB!
- Upgrade the virtual machine configuration version to version 8.0 using PowerShell ( one-liners )
- Production Checkpoints on Hyper-V 2016
- Host Resource Protection on Hyper-V 2016
- AVMA on Windows Server 2016
Thanks for reading!