Why a two-node Proxmox cluster freezes, and how a QDevice vote fixes it
A two-node Proxmox cluster can lock itself up because losing either node leaves the survivor with exactly half the votes, which is not a majority. Without quorum, the cluster filesystem at /etc/pve goes read-only, blocking guest starts, config changes and backups even though the surviving node is healthy. Adding a QDevice, a small external voter that can run on a Raspberry Pi or similar always-on Linux box, provides a third vote so the survivor keeps quorum. The QDevice must run on separate hardware, since placing it on a cluster node would remove two votes if that node fails. Unstable links, such as Wi-Fi with high jitter, can also make a cluster appear broken by causing nodes to repeatedly drop out and rejoin.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in