37
submitted 6 months ago by makmarian@kbin.social to c/proxmox@lemmy.world

Latest announcements for Proxmox.

you are viewing a single comment's thread
view the rest of the comments
[-] possiblylinux127@lemmy.zip 2 points 6 months ago* (last edited 6 months ago)

The problem with 2 nodes is there is no way to identity which node has the issue. From the hosts perspective all it "knows" is that the other node isn't reachable. Technically it could assume that it is the functional one but there is also the possibility that both machines assume they are the working one and then spin up the same VM.

You can cluster two nodes but as soon as one node can't reach the other everything freezes to prevent loss of consensus.

The reason I suggest 5 nodes is because 3 only gives the possibility for one node to fail. If one fails and then the remaining 2 can't sort out what is happening the cluster freezes to prevent loss of consensus. Also having 5 machines means you have more flexibility.

I also want to point out that you need fast networking for HA but I'm sure you already know that.

this post was submitted on 24 Apr 2024
37 points (100.0% liked)

Proxmox

1052 readers
3 users here now

Proxmox VE is a complete, open-source server management platform for enterprise virtualization. It tightly integrates the KVM hypervisor and Linux Containers (LXC), software-defined storage and networking functionality, on a single platform. With the integrated web-based user interface you can manage VMs and containers, high availability for clusters, or the integrated disaster recovery tools with ease.

Proxmox VE Official site

K3S on Proxmox LXC

founded 1 year ago
MODERATORS