Fix dag processor crash by ignoring callbacks from other bundles #57192
Conversation
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
When the dag Processor is made to run specific bundle, it previously attempted to process callback requests for bundles it does not own, leading to a StopIteration in render_log_filename due to missing bundle references. Now, fetch_callbacks only enqueues callbacks whose bundle_name matches one of the manager’s active bundles, leaving others in the DB for the correct processor to handle. closes: apache#57081
ephraimbuddy
added
the
backport-to-v3-1-test
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: |
Contributor
|
Just to add internally we just partitioned the total dags into 4 folders with each dag processor for the folder as bundle. But each dag processor had access to all dags sharing common file system too for logs so we just used the bundle name as log file name as a workaround but this is the correct fix. Thanks. |
ephraimbuddy
added a commit
to astronomer/airflow
that referenced
this pull request
Oct 27, 2025
…che#57192) When the dag Processor is made to run specific bundle, it previously attempted to process callback requests for bundles it does not own, leading to a StopIteration in render_log_filename due to missing bundle references. Now, fetch_callbacks only enqueues callbacks whose bundle_name matches one of the manager’s active bundles, leaving others in the DB for the correct processor to handle. closes: apache#57081 (cherry picked from commit 3b97c94)
ephraimbuddy
added a commit
that referenced
this pull request
Oct 27, 2025
) (#57330) When the dag Processor is made to run specific bundle, it previously attempted to process callback requests for bundles it does not own, leading to a StopIteration in render_log_filename due to missing bundle references. Now, fetch_callbacks only enqueues callbacks whose bundle_name matches one of the manager’s active bundles, leaving others in the DB for the correct processor to handle. closes: #57081 (cherry picked from commit 3b97c94)
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.
When the dag Processor is made to run specific bundle, it previously attempted to process callback requests for bundles it does not own, leading to a StopIteration in render_log_filename due to missing bundle references.
Now, fetch_callbacks only enqueues callbacks whose bundle_name matches one of the manager’s active bundles, leaving others in the DB for the correct processor to handle.
closes: #57081