-
Notifications
You must be signed in to change notification settings - Fork 29
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
Set up JobSet failure policy on workloads #308
Open
IrvingMg
wants to merge
1
commit into
main
Choose a base branch
from
feature/set-up-jobset-failure-policy
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
This is great to use failure policy!! Looking forward to this change.
I named this argument poorly -- its intent is to allow for the workload to restart additionally on user code failures when set. The range of exit codes this should specify is anything that a user would specify like 1,2,...
Some system level exit codes that should always restart the job are 42, 143. Probably should ask GKE folks what other system level exit codes exist. These should always restart the job and should be set / or assumed in the pod failure policy to restart by default.
For background some customers depend on xpk to restart the job in system failure cases by default and avoid user errors (like code typos) from restarting their workload. So this is the default case.
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 be honest, I don't think anyone actually wants a user error to restart the job so the ideal choice in my opinion is to remove the "args.restart_on_user_code_failure" argument and just "restart the job in system failure cases by default and avoid user errors (like code typos) from restarting their workload". Since now with the failure policy support we can do this.
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.
Thanks for the information. Then, to sum up:
restart-on-user-code-failure
flag but allow users to pass additional exit codes for restarting workload.Is that correct? And how is the user going to pass these additional exit codes, should we have another flag for that?
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.
@Obliviour can you confirm those are the changes needed?