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
Bug: After deployment of linux formulas and salt states
/etc/security/limits.conf are not applying, as result connections
to mysql failed with error (pymysql.err.OperationalError)
(1040, u'Too many connections')
Solution: create mysql.overide, where ulimit is set to 102400
Closed-bug: PROD-8427