In Corosync 1.x there was a limit on the maximum number of active nodes in a corosync cluster - broswing the mailing list says 64 hosts. The Pacemaker 1.1 documentation says scalability goes up to 16 nodes. The Pacemaker 2.0 documentation says the same, although I can't find a maximum number of nodes in Corosync 3.
https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Remote/ discusses deployments up to 64 hosts but it appears to reference Pacemaker 1.16.
With the arrival of Corossync 3.x (and Pacemaker 2.x) how large a cluster can be supported? If we want to get to a cluster with 100+ nodes, what are the best design approaches, especially if there is no clear hierarchy to the nodes in use (i.e. all of the hosts are important!).
Are there performance implications when comparing the operation of a pacemaker remote node to a full stack pacemaker node?
Thanks,
Toby Haynes
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
