ddl, owner: refresh ddl sequence cache after becoming the owner (#35516) #35713
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 #35516 to release-6.1
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/35713
After apply modifications, you can push your change to this PR via:
Signed-off-by: wjhuang2016 huangwenjun1997@gmail.com
What problem does this PR solve?
Issue Number: close #35513
Problem Summary:
We init the ddl sequence cache when ddl gets start. But if it's not owner anymore, the cache is out of date.
We should refresh it after a TiDB becomes the owner.
What is changed and how it works?
Add a callback function for ownerManager.
Check List
Tests
As I did in seq_num may be duplicate #35513, the DDL sequence is unique now.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.