Deployer is unable to set MariaDB memory usage

Bug #1736206 reported by aeva black
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Triaged
Wishlist
Unassigned

Bug Description

The current galera.cnf.j2 template does not provide any mechanism to the deployer to control the memory usage of InnoDB. It should, at a minimum, allow setting innodb_buffer_pool_size; 8192MB is not necessarily suitable to every environment.

Current template code:

{% set dynamic_pool_size_mb = (hostvars[inventory_hostname]['ansible_memtotal_mb'] * 0.4) | round | int %}
{% if dynamic_pool_size_mb < 8192 %}
innodb_buffer_pool_size = '{{ dynamic_pool_size_mb }}M'
{% else %}
innodb_buffer_pool_size = '8192M'
{% endif %}

Suggested resolution: include a variable in the role which would allow the deployer to set dynamic_pool_size_mb. If not set, retain current behavior.

Revision history for this message
Eduardo Gonzalez (egonzalez90) wrote :

Hi, you can override config files values.

/etc/kolla/config/galera.cnf or /etc/kolla/config/<hostname>/galera.cnf

[mysqld]
innodb_buffer_pool_size = 'valueMB'

Changed in kolla:
importance: Undecided → Wishlist
status: New → Triaged
affects: kolla → kolla-ansible
Chason Chan (chen-xing)
Changed in kolla-ansible:
assignee: nobody → Chason Chan (chen-xing)
Chason Chan (chen-xing)
Changed in kolla-ansible:
assignee: Chason Chan (chen-xing) → nobody
Tom Fifield (fifieldt)
tags: added: low-hanging-fruit
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.