Hi Daniel, No objection but just a (late arrival) question I had...
The `Backfill.max_active_runs` Will be measured, limited and counted irrespective of the `DAG.max_active_runs` and irrespective of the real actual load? Assuming `DAG.max_active_runs == 10` and currently 5 DAGs are running from manual triggers or schedule, the Backfill will cound the runs from 0 to backfill-max irrespective of parallel schedule? (Total active run counter will not subtract the actual running from the Backfill limit to have the Backfill limit as a overall cumulative cap). Two separate counters and run limits. Jens On 07.10.24 18:23, Daniel Standish wrote:
Alright so since folks don't seem to concerned with my proposal in the discussion thread<https://lists.apache.org/thread/cmh0klwncry0m8h8s6jyjg2wkkgwjn9h>, I am running a formal lazy consensus vote before updating the AIP to reflect the decision. The proposal: DAG.max_active_runs will apply to non-backfill dag runs and will *not* apply to backfill dag runs. Backfill.max_active_runs is a required param for backfills and is evaluated entirely separately from DAG.max_active_runs. In other words, DAG.max_active_runs is not considered at all for dag runs that are part of a backfill. Only the max_active_runs for that backfill is considered. This vote will run from now until Thursday October 10 at 10am America/Los_Angeles time.
