Generate a fresh EmrContainerOperator request token on each task attempt#69625
Merged
vincbeck merged 1 commit intoJul 10, 2026
Merged
Conversation
EmrContainerOperator fixed its client idempotency token once at construction. When the same operator instance was reused across task retries, every attempt resent that token, so EMR on EKS returned the original job run instead of starting a new one. A retry after a transient submit or startup failure therefore replayed the failed run and could never recover. The default token is now resolved on each execute() call, so a task retry starts a genuinely new job run. An explicitly supplied token is still used verbatim, preserving intentional idempotency for callers who want repeated submissions to collapse to one run.
boring-cyborg
Bot
added
area:providers
provider:amazon
vincbeck
approved these changes
Jul 8, 2026
seanghaeli
approved these changes
Jul 8, 2026
joshuabvarghese
pushed a commit
to joshuabvarghese/airflow
that referenced
this pull request
Jul 16, 2026
…mpt (apache#69625) EmrContainerOperator fixed its client idempotency token once at construction. When the same operator instance was reused across task retries, every attempt resent that token, so EMR on EKS returned the original job run instead of starting a new one. A retry after a transient submit or startup failure therefore replayed the failed run and could never recover. The default token is now resolved on each execute() call, so a task retry starts a genuinely new job run. An explicitly supplied token is still used verbatim, preserving intentional idempotency for callers who want repeated submissions to collapse to one run.
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
3 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.
EmrContainerOperator fixed its client idempotency token once at construction. When the same operator instance was reused across task retries, every attempt resent that token, so EMR on EKS returned the original job run instead of starting a new one. A retry after a transient submit or startup failure therefore replayed the failed run and could never recover.
The default token is now resolved on each execute() call, so a task retry starts a genuinely new job run. An explicitly supplied token is still used verbatim, preserving intentional idempotency for callers who want repeated submissions to collapse to one run.
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.