Bug 1301724 - Galera resource agent should not require passing open-files-limit as a meta option
Galera resource agent should not require passing open-files-limit as a meta o...
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents (Show other bugs)
7.3
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Damien Ciabrini
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-25 15:25 EST by Damien Ciabrini
Modified: 2017-06-28 10:11 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Damien Ciabrini 2016-01-25 15:25:39 EST
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.