Mark Goddard 86f373a198 Fixes for MariaDB bootstrap and recovery ... * Fix wsrep sequence number detection. Log message format is 'WSREP: Recovered position: <UUID>:<seqno>' but we were picking out the UUID rather than the sequence number. This is as good as random. * Add become: true to log file reading and removal since I4a5ebcedaccb9261dbc958ec67e8077d7980e496 added become: true to the 'docker cp' command which creates it. * Don't run handlers during recovery. If the config files change we would end up restarting the cluster twice. * Wait for wsrep recovery container completion (don't detach). This avoids a potential race between wsrep recovery and the subsequent 'stop_container'. * Finally, we now wait for the bootstrap host to report that it is in an OPERATIONAL state. Without this we can see errors where the MariaDB cluster is not ready when used by other services. Change-Id: Iaf7862be1affab390f811fc485fd0eb6879fd583 Closes-Bug: #1834467		2019-07-05 09:20:34 +00:00
..
defaults	Add new option to perform an on-demand backup of MariaDB	2018-11-22 09:20:59 +00:00
handlers	Fixes for MariaDB bootstrap and recovery	2019-07-05 09:20:34 +00:00
meta	Reduce dependencies on the dest nodes	2015-08-06 01:32:05 +00:00
tasks	Fixes for MariaDB bootstrap and recovery	2019-07-05 09:20:34 +00:00
templates	Fix MariaDB 10.3 upgrade	2019-03-23 10:21:37 +00:00