Backport of cli: non-service jobs on job restart -reschedule into release/1.6.x
#19223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-nomad-core
force-pushed
the
backport/b-cli-handle-job-restart-types/heavily-frank-stingray
branch
from
2fb7712
to
37f23c3
Compare
hc-github-team-nomad-core
force-pushed
the
backport/b-cli-handle-job-restart-types/heavily-frank-stingray
branch
from
a36557c
to
5fe319a
Compare
vercel
bot
temporarily deployed
to
Preview – nomad-storybook-and-ui
lgfa29
deleted the
backport/b-cli-handle-job-restart-types/heavily-frank-stingray
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #19147 to be assessed for backporting due to the inclusion of the label backport/1.6.x.
The below text is copied from the body of the original PR.
The
-rescheduleflag 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
-rescheduleflag 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
Overview of commits