[GitHub] [airflow] Taragolis commented on issue #29524: Possible deadlock when max_active_runs maxed + depends_on_past = True

["Taragolis (via GitHub)" <gi...@apache.org>]

Taragolis commented on issue #29524:
URL: https://github.com/apache/airflow/issues/29524#issuecomment-1430351066

   I can't say that this is a bug. Everything work as expected.
   With `depends_on_past = True` scheduler can't start task if state for previous interval is `failed`
   When you restart tasks there is new active DagRun created but with `max_active_runs` set to `1` it queued.
   
   The same situation could happen even if you set `max_active_runs` greater that `1`. Simple sample you have schedule interval 10 minutes and `max_active_runs` set to `16` in midnight one task failed, and after 3 hour you have 16 DagRun in `running` state which wait each other, and 20 in `queued`
   
   But again, this expected behaviour when `depends_on_past` set to `True`
   
   


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org