On Wed, Aug 10, 2022 at 7:10 AM Michael Reichert <r...@de.ibm.com> wrote: > > Hi, > > > I would have a question regarding the maximum number of cluster nodes > supported by Corosync 3.x and Pacemaker 2.1. > > On the https://clusterlabs.org entry page one can find the following > statement: > > „We support many deployment scenarios, from the simplest 2-node standby > cluster to a 32-node active/active configuration.“ > > > But in the “Scaling a Pacemaker Cluster” chapter - > https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Remote/html/intro.html - > one can find this contrary statement: > > „In a basic Pacemaker high-availability cluster [1] each node runs the full > cluster stack of Corosync and all Pacemaker components. This allows great > flexibility but limits scalability to around 16 nodes.“ > > > Is this just a documentation inconsistency from a previous release?
Thanks, Michael. Yes, and we're actually in the process of updating the source for the Pacemaker Remote doc right now. > > > > Btw, current Linux distros like Redhat or SUSE both mention a 32 node upper > limit, too: > > https://access.redhat.com/articles/3069031 > > https://documentation.suse.com/sle-ha/15-SP1/html/SLE-HA-all/cha-ha-concepts.html > > > > Thanks in advance! > > > > Regards, > > Michael > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
