Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug and a separate one about DHCP were turned into a new section of the Pacemaker reference for RHEL 7 that should be added to the RHEL 6 document as well.

+++ This bug was initially created as a clone of Bug #1373624 +++

The RHEL 7 HA Add-On Reference only mentions the 16-node limit for clusters as an aside in the section on Pacemaker remote. This needs to be included in a more prominent place.

(And also added to the RHEL 6 Pacemaker manual)

Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information:

--- Additional comment from Steven J. Levine on 2016-09-15 12:41:23 EDT ---

This limitation has been added to the 7.3 draft as part of section 1.5:

http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Enterprise_Linux-7-High_Availability_Add-On_Reference%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#s1-configfileoverview-HAAR

One thing that I would add in the section about the 16 node limitation is that by utilizing pacemaker_remote you can go far above 16 nodes (I don't have the actual limits for pacemaker remote, but I will see if I can find them out).

Chris:  The actual note about 16-nodes in the RHEl 7 doc does specify that you can use pacemaker remote to get around this (although it doesn't give an upper limit).

Red Hat does not support cluster deployments greater than 16 full cluster nodes. It is possible, however, to scale beyond that limit with remote nodes running the pacemaker_remote service. For information on the pacemaker_remote service, see Section 9.3, “The pacemaker_remote Service”.

Section 1.4 here:

http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Enterprise_Linux-6-Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#s1-configconsider-HAAR

The RHEL 6 document on the portal now contains this new section, as section 1.4:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Configuring_the_Red_Hat_High_Availability_Add-On_with_Pacemaker/s1-configconsider-HAAR.html