-
Notifications
You must be signed in to change notification settings - Fork 728
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
server: Make gc_worker's service safepoint special #3146
server: Make gc_worker's service safepoint special #3146
Conversation
Signed-off-by: MyonKeminta <[email protected]>
/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.
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
@rleungx PTAL. Can this be merged? |
server/core/storage.go
Outdated
@@ -45,6 +45,8 @@ const ( | |||
componentPath = "component" | |||
customScheduleConfigPath = "scheduler_config" | |||
encryptionKeysPath = "encryption_keys" | |||
// GCWorkerServiceSafePointID is the ID of GCWorker's service GC safe point. | |||
GCWorkerServiceSafePointID = "gc_worker" |
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.
How about changing this name to make it private?
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.
It's used in test in tests/client/client_test.go .
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.
prefer to use "gc_worker" directly in tests
Signed-off-by: MyonKeminta <[email protected]>
…nKeminta/pd into m/gcworker-service-safepoint
/rebase |
/run-all-tests |
/merge |
@disksing: It seems you want to merge this PR, I will help you trigger all the tests: 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 tidb-community-bots/prow-config repository. |
Can merge label has been added. Git tree hash: 46a717b
|
/merge |
@MyonKeminta: It seems you want to merge this PR, I will help you trigger all the tests: 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 tidb-community-bots/prow-config repository. |
@MyonKeminta: you cannot merge your own PR. 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 tidb-community-bots/prow-config repository. |
/run-integration-lightning-test |
CI failed on lightning's test because lightning sets empty string as serviceID, while this PR added non-empty check. |
sad story. Should we update the lightning test? |
I thin lightning should fix the bug that it didn't set service ID. By the way it's lucky we used |
… or perhaps another choice is to remove the empty check from this PR first to merge this PR quickly, and add the empty check in another PR... Then people who tries to use old versions of lightning on new tidb cluster will get the unfriendly error... |
Do we need to add support in |
@HunDunDM Sorry I didn't get it. What to recover? |
/merge |
@leoppro: It seems you want to merge this PR, I will help you trigger all the tests: /run-all-tests 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 tidb-community-bots/prow-config repository. |
@leoppro: adding 'status/cam-merge' is restricted to committers in list. 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 tidb-community-bots/prow-config repository. |
/run-all-tests |
/run-all-tests |
/run-integration-lightning-test tidb-lightning=pr/460 |
/run-all-tests |
/run-integration-lightning-test |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-4.0 in PR #3173 |
Signed-off-by: MyonKeminta <[email protected]>
* server: Make gc_worker's service safepoint special Signed-off-by: MyonKeminta <[email protected]> * Address comments Signed-off-by: MyonKeminta <[email protected]> Co-authored-by: MyonKeminta <[email protected]> Signed-off-by: MyonKeminta <[email protected]>
* server: Make gc_worker's service safepoint special Signed-off-by: MyonKeminta <[email protected]> * Address comments Signed-off-by: MyonKeminta <[email protected]> Co-authored-by: MyonKeminta <[email protected]> Signed-off-by: MyonKeminta <[email protected]> Co-authored-by: MyonKeminta <[email protected]> Co-authored-by: MyonKeminta <[email protected]>
Signed-off-by: MyonKeminta [email protected]
What problem does this PR solve?
Fixes #3136
What is changed and how it works?
This PR makes service safepoint with
gc_worker
a special one:0
Therefore, gc_worker's service safepoint is no longer symmetrical to other services' safepoints.
By the way, this PR also disallowed registering service safepoint with empty ID.
I'm not sure if returning
errors.New(...)
is a proper way to report errors. If it's not, I need better suggestions.cc @leoppro
Check List
Tests
Code changes
-
Side effects
Related changes
Release note