-
Notifications
You must be signed in to change notification settings - Fork 51
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
Support atomic JobSets #689
Comments
@osigurdson for atomic/group scheduling, we usually recommend users use Kueue. Here is an example from the docs. Let us know if this looks like it will address the issue/use case you've described here. |
Thanks @danielvegamyhre. I will give it a try. |
It seemed to lead to a lot of thrashing: $ k get pods Perhaps misconfigured but a basic Job object ran ok. kueue.yaml jobset.yaml job.yaml This seemed to work ok and created an associated workload, etc. Some logs from jobset controller manager 2024-10-25T03:29:01Z LEVEL(-2) Reconciling JobSet {"controller": "jobset", "controllerGroup": "jobset.x-k8s.io", "controllerKind": "JobSet", "JobSet": {"name":"js-1","namespace":"default"}, "namespace": "default", "name": "js-1", "reconcileID": "6843f06a-02c0-454d-a466-47c4d150c49e", "jobset": {"name":"js-1","namespace":"default"}} |
What would you like to be added:
It would be great if the pods of a given job set were scheduled atomically.
Why is this needed:
When running multiple JobSets, the pods of individual job sets do not start atomically. Shown in the output below, jobset 1 and jobset 3 have individual parts running but not the entire jobset. This could lead to deadlock as JobSets can never get the necessary resources to complete.
$ k get pods
NAME READY STATUS RESTARTS AGE
js-1-part1-0-0-qz88c 0/1 Pending 0 4s
js-1-part2-0-0-dhgnv 1/1 Running 0 4s
js-2-part1-0-0-jqd9m 0/1 Pending 0 4s
js-2-part2-0-0-qxcsx 0/1 Pending 0 4s
js-3-part1-0-0-lqpv4 0/1 Pending 0 4s
js-3-part2-0-0-dvh5g 1/1 Running 0 4s
js-4-part1-0-0-472hl 1/1 Running 0 4s
js-4-part2-0-0-ds9js 1/1 Running 0 4s
js-5-part1-0-0-plpm5 1/1 Running 0 4s
js-5-part2-0-0-zprwq 1/1 Running 0 4s
The text was updated successfully, but these errors were encountered: