Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Writing on a slave causes replication breakage when switching over #10

Closed
tanji opened this issue Oct 6, 2015 · 0 comments
Closed

Writing on a slave causes replication breakage when switching over #10

tanji opened this issue Oct 6, 2015 · 0 comments
Labels
Milestone

Comments

@tanji
Copy link
Owner

tanji commented Oct 6, 2015

As any write on a slave will change current_pos to include the GTID of the write on the slave, when switching over, the slave will look for that GTID in the new master. This will cause replication to break.

Possible solutions: use gtid_slave_pos to initialize replication. Parse gtid_binlog_state to get the correct GTID.

@tanji tanji added the bug label Oct 6, 2015
@tanji tanji added this to the 0.5.0 milestone Oct 6, 2015
@tanji tanji closed this as completed Oct 6, 2015
tanji pushed a commit that referenced this issue Oct 6, 2015
Write dummy transaction on master and use gtid_slave_pos to reinitialize
replication
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant