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

Race condition when fail-over chlid cluster #417

Closed
rdemongeot opened this issue Mar 30, 2022 · 1 comment
Closed

Race condition when fail-over chlid cluster #417

rdemongeot opened this issue Mar 30, 2022 · 1 comment
Assignees
Labels
Milestone

Comments

@rdemongeot
Copy link

Hello,

As discussed per Skype, we have found a possible race condition when fail-over a child cluster.

Parent-stream1 --------+
                                   +-->  child-s1 (old primary) --------> child-s2 (new primary)
Parent-stream2 --------+

to migrate to

Parent-stream1 --------+
                                   +-->  child-s2 (new primary) --------> child-s1 (old primary)
Parent-stream2 --------+

During the operation, the child S1 was reconfigured with "MASTER_USE_GTID=CURRENT_POS" (expected)
but REJOIN Module reconfigure it as "MASTER_USE_GTID=SLAVE_POS" making search for a very old GTID not found into the new primary binary log.

@svaroqui svaroqui self-assigned this Apr 13, 2022
@svaroqui svaroqui added the bug label Apr 13, 2022
@svaroqui svaroqui added this to the 2.2.19 milestone Apr 13, 2022
@svaroqui
Copy link
Collaborator

Please reopen if not fixed

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

2 participants