Repository navigation
model-serving: back off repeated failure recovery - #1970
Open
kube-gopher wants to merge 1 commit into
Open
kube-gopher wants to merge 1 commit into
kube-gopher wants to merge 1 commit into
Conversation
Signed-off-by: kube-gopher <jzlyy68@gmail.com>
volcano-sh-bot
requested review from
LiZhenCheng9527,
YaoZengzeng,
git-malu and
hzxuzhonghu
November 6, 2026 08:08
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Member
Author
|
/remove-kind feature |
kube-gopher
marked this pull request as ready for review
November 6, 2026 08:14
This branch has not been deployed
This file contains hidden or 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
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.
What type of PR is this?
/kind enhancement
What this PR does / why we need it:
ServingGroupRecreate), the Role instance (RoleRecreate), or the Pod (None).max(restartGracePeriodSeconds, backoff), where the backoff is 10s, 20s, 40s, and so on, capped at 5m.DisruptionTarget=True) and Pods deleted by others don't count.RecoveryBackOffcondition and aRecoveryBackOffWarning event. The condition only appears after a unit has actually backed off.--recovery-backoff-base,--recovery-backoff-max, and--recovery-backoff-reset, with Helm values underworkload.controllerManager.recoveryBackoff.--recovery-backoff-base=0srestores the old behavior.Which issue(s) this PR fixes:
Fixes #1951
Bug evidence (required for bug-related PRs):
Special notes for your reviewer:
Does this PR introduce a user-facing change?: