In case of mysql failed it shows different values for different nodes.
After this fix it ll show actual cluster size
Change-Id: I2fcb23418d6de3e03108a1c66a6ebb6ee5b64008
Closes-Bug: PROD-17416
This patch removes separate state galera.ssl as it was previously
wrongly introduced. Instead include ssl tasks to master/slave when
ssl is enabled.
This fixes missing requirements when applying separate states.
Ensure that mysql package is installed before changing group
ownership for ssl files to mysql, as group will be added by mysql
packages.
Fix ssl inital configuration. SSL settings are not applied during
service reload, we have to add them during initial galera cluster
start.
Change-Id: Iff9a268000c3e5e722cc6e197cfd223ec1015f73
Related-Prod: PROD-16695
Make max_connections and innodb_buffer_pool_size configurable
through soft params instead of hard.
Change-Id: Id0bb8f6b6091289275864bf4dd6a6890d11b4782
The buffer_pool_size parameter should be a integer value when followed
by a memory unit (eg '1024M', not '1024.1M'). Otherwise the MySQL
doesn't start properly.
Change-Id: I5dfad49a8e44a40ae87c5e8e0b033dcd73dc2837
Usage:
galera:
master:
innodb_buffer_pool_size: 1024M
slave:
innodb_buffer_pool_size: 1024M
If innodb_buffer_pool_size is not set then 35% of the available
ram will be allocated for the buffer pool.
Change-Id: Iaffa3f5b4ded8bc838f9d707916e360ed873c13b
Because the current timeout interval is too short in some environments.
The change also adds information messages to bootstrap scripts
Change-Id: I295da792349f5864a484e3eb318342dcc31fffab
Galera master installation hangs on installation
mysql-server-wsrep-5.6. It seems that log_error is not working,
because of next message: "mysqld_safe Can't log to error log and
syslog at the same time. Remove all --log-error configuration
options for --syslog to take effect." Using "syslog = yes" instead
of log_error makes it works without any other changes.
Change-Id: I39a8a87ed048557c19f3843b97c75469385e4978
Closes-bug: PROD-9065