koord-scheduler: retrieve reservationInfo from cache first in preFilter hook#906
Conversation
af00a62 to
0699156
Compare
Codecov ReportBase: 66.63% // Head: 66.65% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #906 +/- ##
==========================================
+ Coverage 66.63% 66.65% +0.01%
==========================================
Files 238 238
Lines 27675 27682 +7
==========================================
+ Hits 18442 18451 +9
- Misses 7965 7967 +2
+ Partials 1268 1264 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
|
@saintube please review the PR |
|
/milestone v1.2 |
1118d2a to
68a19cc
Compare
Signed-off-by: KunWuLuan <kunwuluan@gmail.com>
68a19cc to
afbf4b8
Compare
|
/lgtm |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…er hook (#906) Signed-off-by: KunWuLuan <kunwuluan@gmail.com>
…er hook (koordinator-sh#906) Signed-off-by: KunWuLuan <kunwuluan@gmail.com>
fix: prefilter hook get stale reservation from indexer
currently prefilter hook of resource reservation will list reservations from informer cache and construct reservationInfo to judge whether the pod match the reservation(https://github.com/koordinator-sh/koordinator/blob/main/pkg/scheduler/plugins/reservation/hook.go#L147):
However, reservations in informer cache can be stale because in pervious cycles pods can have reserve the resouce of the reservation, which leads to a failed scheduling of the pod:
How to reproduce:
A reservation with label selector ownership and a deployment: