Skip to content

Conversation

@jmaicher
Copy link
Contributor

@jmaicher jmaicher commented Sep 9, 2024

When the task is marked as success/failed externally and is cleared before the task instance receives SIGTERM, then we should not retry to ensure scheduling invariants (e.g. max_active_runs).

Closes #42093


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

When the task is marked as success/failed externally and is cleared
before the task instance receives SIGTERM, then we should not retry
to ensure scheduling invariants (e.g. max_active_runs).

See apache#42093
session.merge(ti)
session.commit()
raise AirflowException()
raise AirflowTaskTerminated()
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to dedicated exception introduced with #37613

@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale Stale PRs per the .github/workflows/stale.yml policy file label Oct 25, 2024
@github-actions github-actions bot closed this Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale Stale PRs per the .github/workflows/stale.yml policy file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Task with retries can circument max_active_runs limit

1 participant