Mysql max connections not getting set in compressed_ha scenario

Bug #1352095 reported by Ken Schroeder
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cisco Openstack
New
Undecided
Unassigned

Bug Description

In compressed_ha and full_ha scenario following variable is defined.

global_hiera_params/scenario/compressed_ha.yaml:db_type: galera
global_hiera_params/scenario/full_ha.yaml:db_type: galera

in hiera_data/user.common.yaml below is set to configure /etc/mysql/my.cnf values
mysql::server::override_options:
  mysqld:
    bind-address: 192.168.100.11
    max_connections: 8192
    max_connect_errors: 4294967295
  isamchk:
    key_buffer_size: 64M

When galera is the db_type that will not properly configure my.cnf values as mysql::server does not get directly instantiated. Instead using the below when galera db_type is set configures my.cnf properly.
galera::override_options:
  mysqld:
    bind-address: 192.168.100.11
    max_connections: 8192
    max_connect_errors: 4294967295
  isamchk:
    key_buffer_size: 64M

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.