Skip to content
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: add a parameter to mark whether scheduling is allowed on node with expired nodemetric #2076

Merged
merged 1 commit into from
Jun 3, 2024

Conversation

lucming
Copy link
Contributor

@lucming lucming commented May 31, 2024

Ⅰ. Describe what this PR does

add enableScheduleWhenNodeMetricsExpired parameter for loadaware scheduler plugin to mark whether scheduling is allowed on node with expired nodemetric.

it be used to address the following issues:

  1. not allow scheduling when nodemetric expired:avoid pods being scheduled to nodes with high load.
  2. allow scheduling when nodemetric expired:the actual load of the node is very low but the nodemetric is very high. It may be blocked by the filter phase, causing the node to be unable to schedule a new pod anymore. FYI: koord-scheduler: skip checking for nodes whose nodemetrics update time has expired #1563

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it

Ⅳ. Special notes for reviews

V. Checklist

  • I have written necessary docs and comments
  • I have added necessary unit tests and integration tests
  • All checks passed in make test

@koordinator-bot koordinator-bot bot requested review from buptcozy and eahydra May 31, 2024 04:15
@lucming lucming force-pushed the loadaware-enhance branch from 7df176f to cc6262e Compare May 31, 2024 04:16
Copy link

codecov bot commented May 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.58%. Comparing base (8e41abc) to head (79f0893).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2076      +/-   ##
==========================================
- Coverage   68.62%   68.58%   -0.05%     
==========================================
  Files         430      430              
  Lines       39540    39639      +99     
==========================================
+ Hits        27136    27188      +52     
- Misses      10061    10097      +36     
- Partials     2343     2354      +11     
Flag Coverage Δ
unittests 68.58% <100.00%> (-0.05%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@saintube saintube left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PTAL cc @ZiMengSheng

pkg/scheduler/plugins/loadaware/load_aware.go Show resolved Hide resolved
pkg/scheduler/apis/config/v1beta3/types.go Show resolved Hide resolved
@saintube saintube requested a review from ZiMengSheng May 31, 2024 05:52
@saintube saintube added this to the v1.5 milestone Jun 3, 2024
…d on node with expired nodemetric

Signed-off-by: lucming <2876757716@qq.com>
@lucming lucming force-pushed the loadaware-enhance branch from cc6262e to 79f0893 Compare June 3, 2024 03:23
@koordinator-bot koordinator-bot bot added size/L and removed size/S labels Jun 3, 2024
@saintube
Copy link
Member

saintube commented Jun 3, 2024

/lgtm

@ZiMengSheng
Copy link
Contributor

/lgtm

@koordinator-bot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@koordinator-bot koordinator-bot bot merged commit 1bac4d3 into koordinator-sh:main Jun 3, 2024
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants