override file with nofile ulimit for new percona cluster
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Percona Cluster Charm |
New
|
Undecided
|
Unassigned |
Bug Description
The bug report is related to 1905366 [1]. Its fix adds an override file /etc/systemd/
This is fine if percona cluster already exists and the max connection config is set to a new value.
However, if a new percona cluster is created with a max connection value, the above override file is not used because when the percona cluster is created and started for the first time, the started service is <email address hidden>, therefore the override file it uses is /etc/systemd/
This is how it looks like when a new percona cluster is just created.
root@juju-
● mysql.service - Percona XtraDB Cluster daemon
Loaded: loaded (/lib/systemd/
Drop-In: /etc/systemd/
Active: inactive (dead) since Thu 2021-07-01 00:42:27 UTC; 10min ago
Process: 1932 ExecStop=
Main PID: 512 (code=exited, status=0/SUCCESS)
root@juju-
● <email address hidden> - Percona XtraDB Cluster daemon with config /etc/default/
Loaded: loaded (/lib/systemd/
Active: active (running) since Thu 2021-07-01 00:42:34 UTC; 11min ago
Process: 2145 ExecStart=
Process: 2043 ExecStartPre=
Main PID: 2185 (mysqld_safe)
Tasks: 102 (limit: 4703)
CGroup: /<email address hidden>
├─2185 /bin/sh /usr/bin/
└─2808 /usr/sbin/mysqld --basedir=/usr --datadir=
Therefore the charm should create /etc/systemd/
[1] https:/