-
Notifications
You must be signed in to change notification settings - Fork 719
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.
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
tso: refactor the tso service #2803
Conversation
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@Yisaer,Thanks for your review. However, LGTM is restricted to Reviewers or higher roles.See the corresponding SIG page for more information. Related SIGs: scheduling(slack). |
/run-all-tests |
1 similar comment
/run-all-tests |
/run-build-image |
Signed-off-by: JmPotato <[email protected]> Signed-off-by: ZenoTan <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato <[email protected]>
Signed-off-by: JmPotato [email protected]
What problem does this PR solve?
Part of #2759. Refactor the tso service to use
Leadership
andTSOAllocator
. After adding the new feature of local TSO allocator in the future, there will be two kinds of member roles need to be elected, one is PD leader, another is Local TSO Allocator. For more details, you can check this document.What is changed and how it works?
Modify the tso package to be more extendable as a
TSOAllocator
in order to introduce the Local TSO Allocator and new Global TSO Allocator later.Check List
Tests
Code changes
Related changes
Release note