← Back to team overview

maria-developers team mailing list archive

GTID replication and relay_log.info



There's a well-known problem in MySQL that relay_log.info is not
always in sync with the database state, and killing and restarting
server at an unfortunate time will cause it to re-execute last
statement and potentially break replication. Did you fix this
situation with GTIDs and rpl_slave_state table? It looks like with
GTIDs it's really easy to solve the problem -- rpl_slave_state has
GTID of the last executed transaction, so on restart one needs just to
ignore all relay logs and re-connect to master with the last GTID. Did
you do that? If not are you planning to do that?

Thank you,

Follow ups