[GitHub] [airflow] uranusjr commented on issue #18304: User induced deadlock for DAGs with `depends_on_past`

2021-10-17 Thread GitBox
uranusjr commented on issue #18304: URL: https://github.com/apache/airflow/issues/18304#issuecomment-945362143 > A possible fix could be to detect the deadlock situation and automatically move dagrun 2 into queued state, clearing path for the dagrun 1. Not sure if this is feasible from

[GitHub] [airflow] uranusjr commented on issue #18304: User induced deadlock for DAGs with `depends_on_past`

2021-10-07 Thread GitBox
uranusjr commented on issue #18304: URL: https://github.com/apache/airflow/issues/18304#issuecomment-937399559 What's the actionable here? Since the deadlock is induced by the user, should we prevent this from happening by not allowing Task B to be cleared? Or do we somehow resolve that

[GitHub] [airflow] uranusjr commented on issue #18304: User induced deadlock for DAGs with `depends_on_past`

2021-10-06 Thread GitBox
uranusjr commented on issue #18304: URL: https://github.com/apache/airflow/issues/18304#issuecomment-937399559 What's the actionable here? Since the deadlock is induced by the user, should we prevent this from happening by not allowing Task B to be cleared? Or do we somehow resolve that