-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
support basic batch job preempt #738
Conversation
Welcome @carmark! |
@carmark Can you update? |
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: a22d43b0-a181-11ea-b485-534d9f3e4954 |
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: 501f0ad0-a187-11ea-b485-534d9f3e4954 |
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: 58989290-a960-11ea-9161-4f77e253115e |
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: 04fd6a60-a961-11ea-9161-4f77e253115e |
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: 590df760-a965-11ea-9161-4f77e253115e |
@carmark do you have time to make CI happy? |
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: 9b294e80-aacb-11ea-9064-4d6590cbb359 |
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: f0e4f7d0-aaed-11ea-b056-2f6ef3b381c7 |
Signed-off-by: Lei Xue <vfs@live.com>
Signed-off-by: Lei Xue <vfs@live.com>
Signed-off-by: Lei Xue <vfs@live.com>
Signed-off-by: Lei Xue <vfs@live.com>
Travis tests have failedHey @carmark, TravisBuddy Request Identifier: ddc16cb0-aaf2-11ea-b056-2f6ef3b381c7 |
@k82cn @hzxuzhonghu |
cool |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carmark, k82cn 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 |
@@ -247,6 +247,7 @@ func (alloc *Action) Execute(ssn *framework.Session) { | |||
stmt.Commit() | |||
} else { | |||
stmt.Discard() | |||
break |
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.
One question: if break here, then it will not try to schedule other jobs in the same period?
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.
yes.
klog.V(1).Infof("%+v", pod.Status.Conditions) | ||
return nil | ||
} | ||
if _, err := de.kubeclient.CoreV1().Pods(p.Namespace).UpdateStatus(pod); err != nil { |
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.
Why do we need to update just before delete?
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.
To give some clients a hint that why this pod is evicted?
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.
yeah, the operator may find this changes and create another pod for the job.
occupid := jobOccupidMap[job.UID] | ||
preemptable := job.MinAvailable <= occupid-1 || job.MinAvailable == 1 | ||
|
||
preemptable := pJob.Priority > job.Priority |
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.
It seems the preemptFn here now is same as priority
's
@carmark |
fixes: #734