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

emergentlyRestartReplicationOnTopologyInstance fixes #1010

Merged
merged 3 commits into from Nov 24, 2019

Conversation

shlomi-noach
Copy link
Collaborator

@shlomi-noach shlomi-noach commented Nov 7, 2019

  • restart replication fully (both SQL and IO threads)
  • fix concurrency/itration bug
  • slightly more logging

Yesterday we observed a situation where stop slave io_thread; start slave io_thread; was not enough to make a replica identify that it's master is broken. By stopping replication completely I hope this mitigates such behavior.

cc @timvaillancourt

- restart replication fully (both SQL and IO threads)
- fix concurrency/itration bug
- slightly more logging

Yesterday I observed a situation where stop slave io_thread; start slave io_thread; was not enough to make a replica identify that it's master is broken. By stopping replication completely I hope this mitigates such behavior
@shlomi-noach shlomi-noach force-pushed the emerently-restart-repication-logging branch from 2645e5a to 2893aec Compare November 7, 2019 07:57
@shlomi-noach shlomi-noach temporarily deployed to production/mysql_cluster=conductor November 7, 2019 08:05 Inactive
@timvaillancourt
Copy link
Contributor

Thanks @shlomi-noach 👍

@shlomi-noach shlomi-noach had a problem deploying to production/mysql_cluster=conductor November 19, 2019 06:16 Failure
@shlomi-noach shlomi-noach merged commit cc29a72 into master Nov 24, 2019
@shlomi-noach shlomi-noach deleted the emerently-restart-repication-logging branch November 24, 2019 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants