uranusjr commented on issue #49508: URL: https://github.com/apache/airflow/issues/49508#issuecomment-2820844220
I tried to reduce this to a reasonable minimal scenario. This is against main since we did not notice any significant logic changes in the area. * Two dags `1` and `2` both have one single task. Both dags set `max_active_runs=1`. The task simply does `sleep(5)`. * Set `AIRFLOW__SCHEDULER__MAX_DAGRUNS_PER_LOOP_TO_SCHEDULE` to `1`. * Trigger 10 runs for `1`, and then 10 for `2`, both via API (I used a Python script with `requests` so the ordering is deterministic). After triggering, I can observe the scheduler actually alternates between the two dags. It picks up a run from the first dag, and then a run from the second, the first, the second, and so on. Interetingly, I _did not_ see any logs on `max_active_runs` at all; the scheduler seems to just do it out of the box. So I think we’re missing something. Not sure what… -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
