Fix callback files losing priority during queue resort #61232
Merged
+51
−2
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 resorts its file queue by modification time (e.g., after a bundle refresh), files with pending callbacks could lose their position at the front of the queue. This could delay callback execution (like DAG failure callbacks) if those files happened to have older modification times. The fix partitions the queue during resort: callback files stay at the front in their original order, while only regular files are sorted by mtime.
eladkal
approved these changes
Jan 29, 2026
ephraimbuddy
added
the
backport-to-v3-1-test
github-actions bot
pushed a commit
that referenced
this pull request
Jan 30, 2026
…61232) When the DAG processor resorts its file queue by modification time (e.g., after a bundle refresh), files with pending callbacks could lose their position at the front of the queue. This could delay callback execution (like DAG failure callbacks) if those files happened to have older modification times. The fix partitions the queue during resort: callback files stay at the front in their original order, while only regular files are sorted by mtime. (cherry picked from commit f5e70fc) Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Backport successfully created: v3-1-test
|
github-actions bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Jan 30, 2026
…pache#61232) When the DAG processor resorts its file queue by modification time (e.g., after a bundle refresh), files with pending callbacks could lose their position at the front of the queue. This could delay callback execution (like DAG failure callbacks) if those files happened to have older modification times. The fix partitions the queue during resort: callback files stay at the front in their original order, while only regular files are sorted by mtime. (cherry picked from commit f5e70fc) Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 30, 2026
…61232) (#61243) When the DAG processor resorts its file queue by modification time (e.g., after a bundle refresh), files with pending callbacks could lose their position at the front of the queue. This could delay callback execution (like DAG failure callbacks) if those files happened to have older modification times. The fix partitions the queue during resort: callback files stay at the front in their original order, while only regular files are sorted by mtime. (cherry picked from commit f5e70fc) Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
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.
When the DAG processor resorts its file queue by modification time (e.g., after a bundle refresh), files with pending callbacks could lose their position at the front of the queue. This could delay callback execution (like DAG failure callbacks) if those files happened to have older modification times.
The fix partitions the queue during resort: callback files stay at the front in their original order, while only regular files are sorted by mtime.
Was generative AI tooling used to co-author this PR?
Generated-by: Cursor (Clause Opus 4.5)