How do we completely disable HA?

[melsom]

Hello,

How do we completely disable HA on our Proxmox 6 cluster? We accidentally added a VM Resource and now HA is enabled on our cluster. We have had issues with randoms reboots on another cluster due to what seems to be sporadic high latency in the cluster. We want to avoid this on our new cluster.

So, how do we completely disable HA on our cluster? There are no VM Resources which has HA enabled now.

 

[t.lamprecht]

So, how do we completely disable HA on our cluster? There are no VM Resources which has HA enabled now.

Restart those pve-ha-lrm services (under Node → System) where the HA Status (Datacenter → HA) shows something else than "idle".

 

[melsom]

Restart those pve-ha-lrm services (under Node → System) where the HA Status (Datacenter → HA) shows something else than "idle".

Thank you. Have all idle now except one "master". Previously before we managed to add a HA Resource, the list only contained the quorum. I suppose the HA is still active when we have a master + slaves? Tried restarting pve-ha-lrm on the one claimed to be master also.

 

[melsom]

Any clues as to how we can remove the master? The list, before enabling HA only had "quourum", but now also lists the nodes as idle and one master. Thank you!

 

[t.lamprecht]

"idle" means that it does nothing, and doesn't has the watchdog activated, so this is safe as not running at all.

An active master is normally not an issue even with flaky quorum. Else, if you really removed all HA resources configured a simple restart of the pve-ha-crm.service should be enough to get it "idle" again.

 

[mproxk]

Does this mean if I have 4 nodes, I can have 2 act as HA nodes by only adding them in HA / Resources / nodes selection?

 

[UdoB]

Does this mean if I have 4 nodes, I can have 2 act as HA nodes by only adding them in HA / Resources / nodes selection?

Yes. Create a HA group with these two nodes and select "[x] restricted".

If one of these two nodes (with active HA resources) loses network connectivity it will fence itself --> hard reboot. The other two won't do that.