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
The patch deletes deprecated cmd.run function which actually
was defined in salt 2016 as alias for cmd.shell therefore this
change supports backward compatibility.
Change-Id: Idbbf869dfafb39d3bf90cdcb05e626cd563ce8e2
Related-Prod: 17056
There is wrong assumption that when server pillar is
defined the node is galera master, we need to check
actually that it is enabled.
Change-Id: I594c3fbdb1dfc829e7750c2fb1a6d4f5593074b2
When SSL enabled, /etc/mysq directory is created by salt.minion
state with 700 permissions. It prohibits mysql from reading config
file as normal mode is 755. This patch ensures that mode for
/etc/mysql and /etc/mysql/ssl have correct rights.
Change-Id: Icc2a43e7a56c60d30a716f29f0a9ec28c6549429
Related-Prod: ROD-16782
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
command called by service.dead state:
systemd-run --scope systemctl stop mysql.service
More common way is to shut down service using known credentials
Change-Id: I2abe7eeea850333139587347039b1de8a6ea486f
The tag is equal to the address of the server which is quite useless
when using a Unix socket address.
Change-Id: Ia87c30f8ff2176f923982d70b712b10ec6e97f56
Depends-On: I538dbb24602a8ad4aece0a74445db47810099bb9
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
Dennis Dmitriev
Jiri Broulik
Petr Michalec
Ildar Svetlov
Vasyl Saienko
Oleh Hryhorov
Ondrej Vasko
Martin Polreich
Kirill Bespalov
System Administrator
Dmitry Kalashnik
Simon Pasquier
Dmitry Stremkovskiy
Petr Michalec
Thom Gerdes
Jan Cach
teoyaomiqui
Marek Celoud
Jakub Pavlik
Guillaume Thouvenin
Éric Lemoine