-
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
mcs: support placement rules in scheduling server #7200
Labels
type/development
The issue belongs to a development tasks
Comments
ti-chi-bot bot
added a commit
that referenced
this issue
Oct 16, 2023
) close #7200 Store rules into the unified storage rather than the isolated implementation. Signed-off-by: JmPotato <ghzpotato@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Development Task
Now, we can watch the change of placement rules with
ruleWatcher
, but we don't use it in the scheduling server withGetRuleStorage
, which should be supported.BTW, after the change of placement rules, we also need to call
AddSuspectKeyRange
, which is similar to/config/rule [post]
,/config/rule/{group}/{id} [delete]
,/config/rule_group [post]
,/config/rule_group/{id} [delete]
The text was updated successfully, but these errors were encountered: