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.

Bug 1200508

Summary: Need to increase the value of max_connections in Galera to avoid disconnections
Product: Red Hat Enterprise Linux 7 Reporter: Jason Guiditta <jguiditt>
Component: resource-agentsAssignee: David Vossel <dvossel>
Status: CLOSED CURRENTRELEASE QA Contact: cluster-qe <cluster-qe>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.2CC: agk, ajeain, cfeist, cluster-maint, djansa, dvossel, fdinitto, jpena, mburns, morazi, mwagner, rhos-maint, yeylon
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1191519
: 1200976 (view as bug list) Environment:
Last Closed: 2015-03-11 17:14:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1191519, 1200976    

Comment 1 David Vossel 2015-03-11 17:14:27 UTC 
The galera agent has an 'additional_parameter' option that is already exposed to pcs. This option allows us to pass custom arguments directly into mysqld. It turns out that mysqld has an option to set the open files limit "--open-files-limit="

example:
# pcs ... create galera ... additional_parameters="--open-files-limit=4098" ...

Using pcs with these options, we can set the ulimit to whatever we want during the creation of the galera resource.

Full example: Set ulimit to 30,000
#pcs resource create db galera additional_parameters="--open-files-limit=30000" enable_creation=true wsrep_cluster_address="gcomm://node1,node2,node3" meta master-max=3 ordered=true op promote timeout=300s on-fail=block --master

This functionality is already available in the galera ocf script ship. I've tested this and it works. Below is how I verified the agent properly set the ulimit to 4098.

cat /proc/$(pidof mysqld)/limits | grep "Max open files"
Max open files            4098                 4098                 files