-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Lower the RelocateShard priority for removing redundant teams #1853
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
Lower the RelocateShard priority for removing redundant teams #1853
Conversation
|
This turns out to be more complex than I thought. I will wait for the server team remover PR to be merged and then get back to this PR. |
PRIORITY_TEAM_REDUNDANT should be in a different priority band from PRIORITY_MERGE_SHARD and PRIORITY_SPLIT_SHARD, because priority inversion happens within priorities in the same band.
The priority band is calculated by the priority / 100. |
|
Passed 100K random tests. |
|
The local run without workload looks good. |
| } else if (highestPriority >= PRIORITY_TEAM_CONTAINS_UNDESIRED_SERVER) { | ||
| stateSectionObj["healthy"] = true; | ||
| stateSectionObj["name"] = "healthy_removing_server"; | ||
| stateSectionObj["description"] = "Removing storage server"; |
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.
This message looks confusing/scary. Maybe something like "optimizing team servers"?
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.
This is for PRIORITY_TEAM_CONTAINS_UNDESIRED_SERVER which is not touched by this PR.
I'm inclined to keep what it is because undesired server (e.g., the server on the same address with another server) is supposed to be removed.
Resolve the review comment.
|
@fdb-build test windows please |
|
@fdb-build test this please |
|
@fdb-build test this please |
|
@etschannen This PR is ready to be merged. |
This PR solves the Issue #1845.
We reduces the priority for removing redundant teams from 700 to 210, lower than merge or split shard priority.