-
Notifications
You must be signed in to change notification settings - Fork 337
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
koord-scheduler: skip checking for nodes whose nodemetrics update time has expired #1563
koord-scheduler: skip checking for nodes whose nodemetrics update time has expired #1563
Conversation
6ad7ed0
to
f76a7ee
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1563 +/- ##
==========================================
+ Coverage 65.04% 65.20% +0.16%
==========================================
Files 352 352
Lines 36253 36326 +73
==========================================
+ Hits 23580 23686 +106
+ Misses 10931 10899 -32
+ Partials 1742 1741 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
…tric is not updated for a long time Signed-off-by: liuming6 <liuming6@360.cn>
f76a7ee
to
152613d
Compare
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: eahydra 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 |
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
…e has expired (koordinator-sh#1563) Signed-off-by: liuming6 <liuming6@360.cn> Co-authored-by: liuming6 <liuming6@360.cn>
Ⅰ. Describe what this PR does
In some cases,
nodemetric
is not updated for a long time, eg: koordlet be deleted. which will result in nodemetric not being able to report, and if the latest load innodemetric
is very high, it will result in the node not being able to run any pods, even if the actual load is very lowAt this point, the
loadaware
scheduling plugin's calculations should not be counted in the final scheduling result, because the plugin strongly relies onnodemetric
in filter phase: do not handle these nodes that nodemetric have not been updated for a long time
in score phase: score 0 and return directly
Ⅱ. Does this pull request fix one issue?
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist
make test