-
Notifications
You must be signed in to change notification settings - Fork 2k
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
cli: non-service jobs on job restart -reschedule
#19147
Conversation
14f823b
to
4c7e24e
Compare
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.
LGTM although the test failure seems like it could be related and there isa a merge conflict 😬
The `-reschedule` flag stops allocations and assumes the Nomad scheduler will create new allocations to replace them. But this is only true for service jobs. Restarting non-service jobs with the `-reschedule` flag causes the command to loop forever waiting for the allocations to be replaced, which never happens. Allocations for system jobs may be replaced by triggering an evaluation after each stop to cause the reconciler to run again. Batch and sysbatch jobs should not be allowed to be rescheduled as they are expected to run to completion unless stopped.
96e77cd
to
6f2ea97
Compare
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.
LGTM :)
8e4719b
to
a7588e6
Compare
Batch jobs are able to be rescheduled without further steps, but sysbatch jobs never receive a replacement allocation so they are still not allowed to be rescheduled.
a7588e6
to
b21fcde
Compare
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
The
-reschedule
flag stops allocations and assumes the Nomad scheduler will create new allocations to replace them. But this is only true for service jobs.Restarting non-service jobs with the
-reschedule
flag causes the command to loop forever waiting for the allocations to be replaced, which never happens.Allocations for system jobs may be replaced by triggering an evaluation after each stop to cause the reconciler to run again.
Batch and sysbatch jobs should not be allowed to be rescheduled as they are expected to run to completion unless stopped.
Closes #19043