Repository navigation
Force-delete wedged pod so Recreate finishes in one pass - #2080
Merged
Merged
Conversation
… pass A scale-to-0 wait timeout used to abort Recreate and leave the host at Replicas=0. Escalate by deleting the pod so Delete+Create can complete in the same reconcile. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
doDeleteStatefulSet. If a pod does not terminate in time, force-delete it and continue the existing Delete + Create path so Recreate completes in the same pass.Replicas=0when a ClickHouse or Keeper pod hangs on shutdown (Recreate can take a whole shard (or Keeper quorum) down when a pod is slow to delete #2078).NotFound, a real pod-delete failure, a successful wait, and Recreate still creating in the same pass.