-
Notifications
You must be signed in to change notification settings - Fork 288
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
validation(dm): manage validator life cycle #4479
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests |
/run-all-tests |
/run-all-tests |
/run-all-tests |
@lance6716 @Ehco1996 ptal |
/run-dm-integration-test |
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.
rest LGTM
Co-authored-by: Ehco <[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
/run-all-tests |
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.
rest lgtm
) | ||
if revision > 0 { |
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.
can we always use the latest revision? in future we might decouple from etcd, and revision may not be supported in new metadata storage.
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.
in operateSubTaskStage
, we need to get validator stage using revision of the subtask.
although is't right to use latest revision(same result), but it's more clear this way.
/run-all-tests |
/run-all-tests |
/run-all-tests |
/run-verify |
/merge |
@D3Hunter: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
needs merge @lance6716 @Ehco1996 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 2e4bb60
|
What problem does this PR solve?
Issue Number: close #4459
What is changed and how it works?
see issue for validator life cycle description
validator is empty in this pr.
dmctl
command to start/stop validator will be add in later prCheck List
Tests
Code changes
Side effects
Related changes
Release note