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.

Sign up for GitHub

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

Jump to bottom

REPL_INFO should not be used if slave was previously replicating properly #61

Open
dotmanila opened this issue Jan 10, 2017 · 1 comment
Open

REPL_INFO should not be used if slave was previously replicating properly #61

dotmanila opened this issue Jan 10, 2017 · 1 comment

Comments

@dotmanila
Copy link
Contributor

REPL_INFO can be stale - for example, if slave drops from the network for some reason, the agent would reset replication to use the values from REPL_INFO which would be outdated. At worse this can break replication, lucky if the old binlogs does not exists anymore.
@dotmanila
Copy link
Contributor Author

dotmanila commented Jan 10, 2017 •
edited
Loading

tags:#162653 CentOS 6.6, MySQL 5.5, pacemaker with corosync

@dotmanila dotmanila mentioned this issue Mar 9, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dotmanila