Retry EKS resource deletion on transient ResourceInUseException#70260
Open
ramitkataria wants to merge 1 commit into
Open
Retry EKS resource deletion on transient ResourceInUseException#70260ramitkataria wants to merge 1 commit into
ramitkataria wants to merge 1 commit into
Conversation
boring-cyborg
Bot
added
area:providers
provider:amazon
ramitkataria
marked this pull request as draft
July 22, 2026 23:02
Deleting an EKS cluster, nodegroup, or Fargate profile can transiently fail with ResourceInUseException while the resource is still settling from a prior operation. The delete operators and the deferrable delete trigger surfaced that error immediately, failing the task and leaving the resource orphaned. Both the synchronous operators and the async trigger now retry these deletes with exponential backoff until the resource settles, giving up and re-raising only after a bounded timeout so a genuinely wedged resource still fails. With the operators handling this directly, the manual task-level retries in the EKS system test DAGs are no longer needed and are removed.
ramitkataria
force-pushed
the
ramitkataria/eks-delete-retry-resource-in-use
branch
from
July 22, 2026 23:43
c8aa0d2 to
5ff3634
Compare
ramitkataria
marked this pull request as ready for review
July 22, 2026 23:50
Contributor
Author
|
CI will be fixed once #70224 is merged |
vincbeck
approved these changes
Jul 23, 2026
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
2 participants
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.
Deleting an EKS cluster, nodegroup, or Fargate profile can transiently fail with ResourceInUseException while the resource is still settling from a prior operation. The delete operators and the deferrable delete trigger surfaced that error immediately, failing the task and leaving the resource orphaned.
Both the synchronous operators and the async trigger now retry these deletes with exponential backoff until the resource settles, giving up and re-raising only after a bounded timeout so a genuinely wedged resource still fails.
With the operators handling this directly, the manual task-level retries in the EKS system test DAGs are no longer needed and are removed.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.