You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm ready to add preemptionPolicy related logic in reclaim action, but when I'm confused that when the task's preemptionPolicy is Never, do I need to push back the job and queue, continue allowing other tasks or jobs to reclaim resources. You can see that in the reclaim action,
klog.V(3).Infof("PrePredicate for task %s/%s failed for: %v", task.Namespace, task.Name, err)
continue
}
If the task fails to filter in allocatable, Preemptive, PrePredicateFn, the queue will never be pushed back, but whether if other tasks in same jobs or other jobs in same queue can reclaim resources, I'm little bit confused about the logic here, I think when I need to implement the preemptionPolicy, there is need to push the job and queue back to allow others to continue reclaiming.
klog.V(3).Infof("Queue <%s> is overused when considering task <%s>, ignore it.", queue.Name, task.Name)
continue
}
, at line 192, it wraps with !tasks.Empty() loop, so if the task fails to filter in allocatable, it's reasonable to continue here, allow other task to continue allocate.
9.20 updated:
After discussing with @Monokaix@hwdef@lowang-bh , we think there are some problems in reclaim action, need to refactor the reclaim action
Any other relevant information
No response
The text was updated successfully, but these errors were encountered:
Please describe your problem in detail
I'm ready to add
preemptionPolicy
related logic in reclaim action, but when I'm confused that when the task'spreemptionPolicy
isNever
, do I need to push back the job and queue, continue allowing other tasks or jobs to reclaim resources. You can see that in the reclaim action,volcano/pkg/scheduler/actions/reclaim/reclaim.go
Lines 86 to 220 in 0843c0d
volcano/pkg/scheduler/actions/reclaim/reclaim.go
Lines 110 to 112 in 0843c0d
volcano/pkg/scheduler/actions/reclaim/reclaim.go
Lines 116 to 119 in 0843c0d
volcano/pkg/scheduler/actions/reclaim/reclaim.go
Lines 121 to 124 in 0843c0d
volcano/pkg/scheduler/actions/reclaim/reclaim.go
Lines 126 to 129 in 0843c0d
If the task fails to filter in allocatable, Preemptive, PrePredicateFn, the queue will never be pushed back, but whether if other tasks in same jobs or other jobs in same queue can reclaim resources, I'm little bit confused about the logic here, I think when I need to implement the
preemptionPolicy
, there is need to push the job and queue back to allow others to continue reclaiming.You can also see the logic in allocate:
volcano/pkg/scheduler/actions/allocate/allocate.go
Lines 192 to 199 in 0843c0d
!tasks.Empty()
loop, so if the task fails to filter in allocatable, it's reasonable to continue here, allow other task to continue allocate.9.20 updated:
After discussing with @Monokaix @hwdef @lowang-bh , we think there are some problems in reclaim action, need to refactor the reclaim action
Any other relevant information
No response
The text was updated successfully, but these errors were encountered: