Skip to content

Recover Athena queries after worker crashes - #72419

Closed
1fanwang wants to merge 2 commits into
apache:mainfrom
1fanwang:recover-athena-queries
Closed

1fanwang wants to merge 2 commits into
apache:mainfrom
1fanwang:recover-athena-queries

Conversation

@1fanwang

@1fanwang 1fanwang commented Sep 2, 2026 •

Copy link
Copy Markdown
Contributor

A synchronous Athena task submits another query when its worker exits after StartQueryExecution and Airflow retries it. The retry now resumes the stored query. A completed query returns without resubmission; failed, cancelled, or missing queries submit normally.

When Athena no longer recognizes the stored ID, it returns InvalidRequestException: QueryExecution <id> was not found. Only that response for the same query ID triggers replacement; other invalid requests still fail.

AIP-103 task state is used only for synchronous polling. The operator stores the query ID before polling, reconnects active queries, and restores the ID and results link. Deferrable tasks and client_request_token behavior do not change.

Testing

uv run --project providers/amazon pytest providers/amazon/tests/unit/amazon/aws/operators/test_athena.py -xq

The live test drove the real operator execute() path and task state API against fresh SQLite with a local Athena hook stand-in.

UPSTREAM=/tmp/airflow-athena-main
git worktree add --detach "$UPSTREAM" upstream/main
AIRFLOW_HOME="$PWD/.tmp-athena-e2e" \
LEGACY_ATHENA_OPERATOR_PATH="$UPSTREAM/providers/amazon/src/airflow/providers/amazon/aws/operators/athena.py" \
uv run --project providers/amazon pytest -p tests_common.pytest_plugin \
  dev/test_athena_resumability_e2e.py -xvs
git worktree remove "$UPSTREAM"
Raw logs
TASK_STATE_AFTER_CRASH api=query-1 db=query-1
BEFORE stored=query-1 result=query-2 submitted=['query-2']
Reconnecting to existing job external_id=query-1 external_id_key=athena_query_execution_id status=RUNNING
AFTER stored=query-1 result=query-1 submitted=[] operator_id=query-1 link_id=query-1
PASSED
1 passed, 1 warning in 50.94s

Was generative AI tooling used to co-author this PR?
  • Yes (GitHub Copilot CLI (GPT-5.6 Sol))

Generated-by: GitHub Copilot CLI (GPT-5.6 Sol) following the guidelines

Synchronous Athena tasks currently submit a second query when a worker crashes after submission but before polling completes. This can duplicate work and leave the original query running.

Generated-by: GitHub Copilot CLI (GPT-5.6 Sol)
Signed-off-by: 1fanwang <[email protected]>
@boring-cyborg boring-cyborg Bot added area:providers provider:amazon AWS/Amazon - related issues labels Sep 2, 2026
Stored query IDs can disappear before Airflow retries the task. Athena reports that lookup as InvalidRequestException, which otherwise prevents the retry from submitting a replacement.

Generated-by: GitHub Copilot CLI (GPT-5.6 Sol)
Signed-off-by: 1fanwang <[email protected]>
@potiuk potiuk added the closed because of open PR limit Closed as a one-time step of introducing the open pull request limit label Sep 25, 2026
@potiuk

potiuk commented Sep 25, 2026

Copy link
Copy Markdown
Member

Hello @1fanwang - thank you for your contributions to Apache Airflow!

The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 34 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:

These pull requests stay open because maintainers are already engaged in them - they count towards your limit:

This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are.

What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or gh pr reopen <PR_NUMBER> --repo apache/airflow. Reopen the ones you are ready to follow through - keep them rebased, respond to review comments and fix failing checks.

While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack.

Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst.


Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers closed because of open PR limit Closed as a one-time step of introducing the open pull request limit provider:amazon AWS/Amazon - related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants