From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs v2 4/5] pvecm: extend cluster Requirements
Date: Fri, 27 Jun 2025 15:44:52 +0200 [thread overview]
Message-ID: <20250627134455.2065020-5-a.lauterer@proxmox.com> (raw)
In-Reply-To: <20250627134455.2065020-1-a.lauterer@proxmox.com>
by expanding on best practices with background information as to how and
why.
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
Notes:
changes since:
v1:
* rephrase and reformat recommendations for additional corosync links
pvecm.adoc | 26 ++++++++++++++++++++++++--
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 3b9cfc4..d649e26 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -68,9 +68,31 @@ Requirements
* If you are interested in High Availability, you need to have at
least three nodes for reliable quorum. All nodes should have the
same version.
++
+NOTE: For smaller 2-node clusters, the xref:_corosync_external_vote_support[QDevice]
+can be used to provide a 3rd vote.
-* We recommend a dedicated NIC for the cluster traffic, especially if
- you use shared storage.
+* We recommend a dedicated physical NIC for the cluster traffic.
++
+NOTE: The {pve} cluster communication uses the Corosync protocol. It needs consistent
+low latency but not a lot of bandwidth. A dedicated 1 Gbit NIC is enough in
+most situations. It helps to avoid situations where other services can use up
+all the available bandwidth. Which in turn would increase the latency for the
+Corosync packets.
+
+* Additional links for cluster traffic offers redundancy in case the dedicated
+network is down.
++
+NOTE: Corosync supports up to 8 links.
++
+NOTE: To ensure reliable Corosync redundancy, it is essential to have at least
+another link on a different physical network. This enables Corosync to keep the
+cluster communication alive should the dedicated network be down.
++
+NOTE: A single link backed by a bond is not enough to provide Corosync
+redundancy. When a bonded interface fails and Corosync cannot fall back to
+another link, it can lead to asymmetric communication in the cluster, which in
+turn can lead to the cluster losing quorum.
* The root password of a cluster node is required for adding nodes.
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-06-27 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 13:44 [pve-devel] [PATCH docs/manager v2 0/7] by expanding on it in the docs and the UI Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 1/5] pvecm: drop notes about old version incompatibilities Aaron Lauterer
2025-07-16 23:04 ` [pve-devel] partially-applied: " Thomas Lamprecht
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 2/5] pvecm: add anchor for cluster requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 3/5] pvecm: add anchor for corosync exernal vote support Aaron Lauterer
2025-06-27 13:44 ` Aaron Lauterer [this message]
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 5/5] ha-manager: expand requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH manager v2 1/2] ui: cluster create: add recommendations for cluster networks Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH manager v2 2/2] ui: guest import: make sure an external link has target _blank Aaron Lauterer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250627134455.2065020-5-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox