Crash-resistant replication: How to avoid MySQL replication errors
vendredi 4 septembre 2015 à 11:52@jeekajoo shaarlinks
hum mais pourquoi on utilise pas ça au boulot... quand un serveur (sous percona 5.6) reboot tout seul pendant la nuit (d'ailleurs merci aws ec2 pour cette super nuit #sysadminlife).
Actuellement il se produit exactement ceci quand le slave crash entre le commit de transaction et la mise à jour du relay-log.info:
"""
The relay-log.info file contains the position of the slave relay log, which the slave is applying. Somehow, if a crash occurs on the slave between transaction commit and update of relay-log.info, the replication can be inconsistent – indicating that the relay-log.info file may not be in sync on the disk and contains old information. As a result, when the slave starts again it will read old events from the relay log. And because of this the transaction can be applied multiple times.
"""
(Permalink) (Profil)
hum mais pourquoi on utilise pas ça au boulot... quand un serveur (sous percona 5.6) reboot tout seul pendant la nuit (d'ailleurs merci aws ec2 pour cette super nuit #sysadminlife).
Actuellement il se produit exactement ceci quand le slave crash entre le commit de transaction et la mise à jour du relay-log.info:
"""
The relay-log.info file contains the position of the slave relay log, which the slave is applying. Somehow, if a crash occurs on the slave between transaction commit and update of relay-log.info, the replication can be inconsistent – indicating that the relay-log.info file may not be in sync on the disk and contains old information. As a result, when the slave starts again it will read old events from the relay log. And because of this the transaction can be applied multiple times.
"""
(Permalink) (Profil)