> As an aside... Because one node didn't start, and my Proxmox cluster has only two nodes, it can't reach quorum, meaning I can't really make any changes to my other node, and I can't start any containers that are stopped.
I've recently added another Zigbee dongle, that supports Thread, and it happens to share same VID:PID combo as the old dongle, so due to how these were mapped into guest OS, all my light switches stopped working. I had to fix the issue fast.Lesson in here somewhere. Something about about a toaster representing the local intelligence maxima?
RedShift1|3 months ago
QuantumNomad_|3 months ago
snapplebobapple|3 months ago
speed_spread|3 months ago
nightpool|3 months ago
Spivak|3 months ago
For even n>2 you define a tie breaker node in advance and only the partition connected to that node can make a quorum at 50%. For n=2 going from no quorum to quorum requires both nodes but losing a node doesn't lose quorum, and when you lose a node you stop, shoot the other node, and continue. For split brain the fastest draw wins the shootout.
vsviridov|3 months ago
So I went for the AOOSTAR NAS mini-pc as a "proper" solution. Ended up with two machines, so why not join them into the cluster!
Probably can chuck proxmox on a RasPi somewhere, just for quorum purposes :)
znpy|3 months ago
Most homelabbers ignore recommendations because if anything breaks nothing of corporate value is lost and no one's gonna lose their job.
holysoles|3 months ago
vsviridov|3 months ago
Saris|3 months ago