Fix max_active_tis_per_dag for deferred task instances #61769
+354
−8
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.
closes: #61700
Description
Deferred tasks were previously excluded from max_active_tis_per_dag and max_active_tis_per_dagrun concurrency checks. This allowed an unlimited number of tasks to enter the
DEFERREDstate, bypassing configured limits.This PR enforces these limits for
DEFERREDtask instances while ensuring that max_active_tasks (which limits worker slot usage) remains unaffected.Changes:
TASK_CONCURRENCY_EXECUTION_STATESto includeDEFERRED,RUNNING, andQUEUED.dag_run_active_tasks_map.Tests:
Added unit tests covering:
Was generative AI tooling used to co-author this PR?