Log and audit when the partitioned Dag run per-tick cap is reached - #71072
Open
Lee-W wants to merge 2 commits into
Open
Log and audit when the partitioned Dag run per-tick cap is reached#71072Lee-W wants to merge 2 commits into
Lee-W wants to merge 2 commits into
Conversation
boring-cyborg
Bot
added
the
area:Scheduler
Lee-W
force-pushed
the
scheduler-partition-cap-visibility
branch
2 times, most recently
from
August 4, 2026 14:34
1b505e8 to
aa91e1c
Compare
Emits a scheduler warning on every tick the cap is hit, plus a single `partition dag run cap reached` audit Log row per backlog episode. The audit row is written through `create_session(scoped=False)` so the caller's `@retry_db_transaction` rollback cannot discard it; it must stay ahead of any other write in the tick or the extra connection can lock-contend on SQLite.
Lee-W
force-pushed
the
scheduler-partition-cap-visibility
branch
from
August 4, 2026 14:44
aa91e1c to
ed6751e
Compare
Lee-W
marked this pull request as ready for review
August 4, 2026 15:25
Member
Author
|
cc @TJaniF |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
It's not noticeable when the APDR cap is reached.
What
Emits a scheduler warning on every tick the cap is hit, plus a single
partition dag run cap reachedaudit Log row per backlog episode.The audit row is written through
create_session(scoped=False)so the caller's@retry_db_transactionrollback cannot discard it; it must stay ahead of any other write in the tick or the extra connection can lock-contend on SQLite.Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.