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 1301724 - Galera resource agent should not require passing open-files-limit as a meta option
Summary: Galera resource agent should not require passing open-files-limit as a meta o...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Damien Ciabrini
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-25 20:25 UTC by Damien Ciabrini
Modified: 2017-10-03 13:10 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-03 13:10:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Damien Ciabrini 2016-01-25 20:25:39 UTC
Description of problem:

When the Galera resource agent starts nodes of a galera cluster, it currently relies on the resource's attribute to pass the "open files limit" to mysqld.

Splitting the mysql configuration in two distinct locations (mariadb configuration files and pacemaker cib) is not ideal as it can cause all sort of bad behaviours:

  . increasing "max_connection" in galera config may not work if one forgot to change "open files limit" accordingly in pacemaker resource.

  . starting galera manually while resource is unmanaged in pacemaker will have a different limit.

  . specifying "open files limit" in galera config file and in pacemaker will cause on setting to be overriden, which can be unexpected.

We should have cleaner "open files limit" policy and make sure the resource agent works as expected without relying on resource attribute.


Note You need to log in before you can comment on or make changes to this bug.