-
Notifications
You must be signed in to change notification settings - Fork 3k
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
enhance: Enable node assign policy on resource group (#36968) #37588
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 2.4 #37588 +/- ##
==========================================
+ Coverage 79.65% 80.61% +0.95%
==========================================
Files 1069 1069
Lines 166729 166812 +83
==========================================
+ Hits 132816 134472 +1656
+ Misses 29507 27932 -1575
- Partials 4406 4408 +2
|
issue: milvus-io#36977 with node_label_filter on resource group, user can add label on querynode with env `MILVUS_COMPONENT_LABEL`, then resource group will prefer to accept node which match it's node_label_filter. then querynode's can't be group by labels, and put querynodes with same label to same resource groups. Signed-off-by: Wei Liu <wei.liu@zilliz.com>
Signed-off-by: Wei Liu <wei.liu@zilliz.com>
ff01a33
to
8802e75
Compare
rerun ut |
/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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: congqixia, weiliu1031 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
issue: #36977
pr: #36968
with node_label_filter on resource group, user can add label on querynode with env
MILVUS_COMPONENT_LABEL
, then resource group will prefer to accept node which match it's node_label_filter.then querynode's can't be group by labels, and put querynodes with same label to same resource groups.