Skip to content

Conversation

@ephraimbuddy
Copy link
Contributor

When running multiple deferrable in parallel, triggers are repeatedly added to triggerer queue to create by the update_trigger's method. Then it's being skipped with a warning at the creating_trigger's method. The warning is too many when there're many tasks to defer causing inefficency.

The fix here was to exclude the already queued triggers from the triggers to create and I purposely left the warning log of encountering a trigger already in to_create in case there's another way it could still be possible.

When running multiple deferrable in parallel, triggers are repeatedly
added to triggerer queue to create by the update_trigger's method. Then it's
being skipped with a warning at the creating_trigger's method. The
warning is too many when there're many tasks to defer causing inefficency.

The fix here was to exclude the already queued triggers from the triggers to
create and I purposely left the warning log of encountering a trigger already
in to_create in case there's another way it could still be possible.
@ephraimbuddy
Copy link
Contributor Author

Screenshot 2025-08-12 at 20 53 08

@ashb ashb added the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Aug 13, 2025
@ashb ashb added this to the Airflow 3.0.5 milestone Aug 13, 2025
@ephraimbuddy ephraimbuddy merged commit bfd0bbe into apache:main Aug 13, 2025
59 checks passed
@ephraimbuddy ephraimbuddy deleted the fix-repeated-adding-triggers branch August 13, 2025 08:29
github-actions bot pushed a commit that referenced this pull request Aug 13, 2025
… triggerer (#54438)

When running multiple deferrable in parallel, triggers are repeatedly
added to triggerer queue to create by the update_trigger's method. Then it's
being skipped with a warning at the creating_trigger's method. The
warning is too many when there're many tasks to defer causing inefficency.

The fix here was to exclude the already queued triggers from the triggers to
create and I purposely left the warning log of encountering a trigger already
in to_create in case there's another way it could still be possible.
(cherry picked from commit bfd0bbe)

Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
@github-actions
Copy link

Backport successfully created: v3-0-test

Status Branch Result
v3-0-test PR Link

github-actions bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Aug 13, 2025
… triggerer (apache#54438)

When running multiple deferrable in parallel, triggers are repeatedly
added to triggerer queue to create by the update_trigger's method. Then it's
being skipped with a warning at the creating_trigger's method. The
warning is too many when there're many tasks to defer causing inefficency.

The fix here was to exclude the already queued triggers from the triggers to
create and I purposely left the warning log of encountering a trigger already
in to_create in case there's another way it could still be possible.
(cherry picked from commit bfd0bbe)

Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
ephraimbuddy added a commit that referenced this pull request Aug 13, 2025
… triggerer (#54438) (#54441)

When running multiple deferrable in parallel, triggers are repeatedly
added to triggerer queue to create by the update_trigger's method. Then it's
being skipped with a warning at the creating_trigger's method. The
warning is too many when there're many tasks to defer causing inefficency.

The fix here was to exclude the already queued triggers from the triggers to
create and I purposely left the warning log of encountering a trigger already
in to_create in case there's another way it could still be possible.
(cherry picked from commit bfd0bbe)

Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:Triggerer backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants