I've been working on developing a pacemaker resource-agent for mariadb
There is a pull request here on github:
I would be very happy for some review (and even testing) of this
resource-agent from somebody with expertise in mariadb replication.
The general idea is to select the master at startup and failure as the
node with the highest GTID.
AFTER_SYNC is used to ensure at least one slave will have all the
mariadb is started with --log-slave-updates to ensure that slaves log
all events, so the binary log on each node should always be complete.
The parameter set on each node is as follows:
SET GLOBAL rpl_semi_sync_slave_enabled='ON', \
I suspect this may be overkill, but I don't have the competence to
I have also found that calling "SHOW SLAVE STATUS;" may take a long time
to display data when the slave is very busy (typically replicating after
a failure). Is there any way to make sure it doesn't block?
All feedback very welcome.
Mailing list: https://launchpad.net/~maria-discuss
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~maria-discuss
More help : https://help.launchpad.net/ListHelp