This repository has been archived by the owner on Nov 24, 2023. It is now read-only.
*: only get master status once when query-status (#1619) #1630
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.
cherry-pick #1619 to release-2.0
You can switch your code base to this Pull Request by using git-extras:
# In dm repo: git pr https://github.com/pingcap/dm/pull/1630
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
originally we get master status in every sync and relay unit, which is redundant because a worker handles only one source
What is changed and how it works?
get master status at worker level
Check List
Tests
Code changes
Related changes