Bug 1301724

Summary: Galera resource agent should not require passing open-files-limit as a meta option
Product: Red Hat Enterprise Linux 7 Reporter: Damien Ciabrini <dciabrin>
Component: resource-agentsAssignee: Damien Ciabrini <dciabrin>
Status: CLOSED NOTABUG QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: agk, cluster-maint, fdinitto, oalbrigt
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-03 13:10:29 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:

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.