Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Adding locate-gtid-errant command #850

Merged
merged 3 commits into from
Mar 28, 2019
Merged

Adding locate-gtid-errant command #850

merged 3 commits into from
Mar 28, 2019

Conversation

shlomi-noach
Copy link
Collaborator

locate-gtid-errant reports the names of the binary logs containing errant GTID for a given instance.

Example usage:

orchestrator-client -c locate-gtid-errant -i my-host:3306
mysql-bin.000001
mysql-bin.000004
mysql-bin.000006

Execution returns with an error when:

  • there is no errant GTID
  • part or all of the errant GTID is purged

@shlomi-noach shlomi-noach temporarily deployed to production/mysql_cluster=conductor March 24, 2019 12:03 Inactive
@shlomi-noach shlomi-noach temporarily deployed to production/mysql_cluster=concertmaster March 24, 2019 12:03 Inactive
@shlomi-noach shlomi-noach temporarily deployed to production/mysql_cluster=conductor March 24, 2019 13:13 Inactive
@shlomi-noach shlomi-noach had a problem deploying to production/mysql_cluster=concertmaster March 24, 2019 13:13 Failure
@shlomi-noach shlomi-noach temporarily deployed to production/mysql_cluster=conductor March 25, 2019 13:04 Inactive
@shlomi-noach shlomi-noach had a problem deploying to production/mysql_cluster=concertmaster March 25, 2019 13:04 Failure
@shlomi-noach
Copy link
Collaborator Author

This PR also adds the which-gtid-errant command, which outputs the errant GTID, if such exists.

@shlomi-noach shlomi-noach merged commit 8adf55e into master Mar 28, 2019
@shlomi-noach shlomi-noach deleted the which-errant branch March 28, 2019 05:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant