Closed grypyrg closed 6 years ago
Looks very interesting.
Can I ask why you decided to remove the engine spec when creating the infra.chk_masterha
table? Seems it could be a way to introduce weird problems if one was to work with an esoteric default-storage-engine
option.
@gcs-github If you use enforce_storage_engine=innodb
(percona server / mariadb) then you get an error while creating a MyISAM
table. See commit df1f5e7
@yoshinorim : Would you please consider merging this PR or provide feedback about it?
There has been an uptick in requests to have super_read_only
support with MHA.
This adds functionality for super_read_only which is in Percona Server & MariaDB. Certain tests are done while the node might still be in read_only, this code disables the super_read_only (and enables read_only) during the tests and during the applying of relay logs.