Support read from specific MySQL Binlog gtid #160
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support read from specific MySQL Binlog gtid.
When reading a highly available MySQL Cluster, a master-slave switch or IP drift occurs and the checkpoint is not updated in a timely way, resulting in a failure to start reading from the checkpoint file due to a change in GTIDs.Since our checkpoints are spaced far apart, this is likely to affect us.
We added the GTID field in the checkpoint file to facilitate our clients to get the accurate GTID.