openstack/openstack-ansible-galera_server
Code Issues Proposed changes

Set the proper amount of open files in systemd

Browse Source 
We used the amount of connections instead of the maximum number
of open files for the systemd unit limit.

The amount of connections are handled by mysql.

Change-Id: Ib82cba87038ac2601b4ff268c6c889dbe2387228
Closes-Bug: #1659060
This commit is contained in:
Jean-Philippe Evrard 2017-01-24 17:45:23 +00:00
parent f8881fe986
commit 79b39d585a
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
releasenotes/notes/fix-wrong-amount-of-open-files-systemd-54af64659bf61518.yaml Normal file
View File

@ -0,0 +1,8 @@
---
fixes:
- Systems using systemd (like Ubuntu Xenial) were
incorrectly limited to a low amount of open files.
This was causing issues when restarting galera.
A deployer can still define the maximum number
of open files with the variable
``galera_file_limits`` (Defaults to 65536).

10
templates/systemd.limits.conf.j2
View File

@ -1,13 +1,5 @@
# {{ ansible_managed }}
{%- set all_calculated_max_connections = [] %}
{%- for galera_node in galera_cluster_members %}
{%- set vcpus = hostvars[galera_node]['ansible_processor_vcpus'] %}
{%- set _ = all_calculated_max_connections.append((vcpus | int > 0) | ternary (vcpus, 2) * 100) %}
{%- endfor %}
{%- set calculated_min_connections = all_calculated_max_connections | min %}
{%- set calculated_max_connections = galera_max_connections | default(calculated_min_connections) %}
[Service]
LimitNOFILE={{ calculated_max_connections }}
LimitNOFILE={{ galera_file_limits }}