MariaDB GTID Relay log working on slave server
You are viewing an old version of this question. View
the current version here.
In MariaDB 10.2 with GTID-based replication, will the relay logs on the slave server be purged if the slave crashes? And, if the slave server is lagging behind and then restarts, will it continue replication from the correct position, or will it have to start from a new position?
Answer
1. Yes, when the slave restarts in GTID-mode (including after a crash), the relay-logs will be discarded and re-fetched from the master. This is MDEV-4698.
2. Yes, whenever the slave restarts, it will continue from the right GTID position. The GTID position is stored transactionally (when using InnoDB) in the table mysql.gtid_slave_pos, so slave will restart from the correct GTID position even after a crash.
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
