[
https://issues.apache.org/jira/browse/AIRFLOW-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508440#comment-16508440
]
andy dreyfuss commented on AIRFLOW-2584:
----------------------------------------
This appears to be related to operators that directly trigger other dags, like
the TriggerDagRunOperator or by using the
experimental.trigger_dag.trigger_dag() function. I can reproduce by triggering
a simple sleep operator over and over after setting dag run concurrency low.
After a few run, they begin to just all get queued indefinitely even though
nothing is running.
> Tasks Never Get DeQueued, No New DagRuns Can Start
> --------------------------------------------------
>
> Key: AIRFLOW-2584
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2584
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
> Affects Versions: Airflow 2.0, Airflow 1.9.0
> Reporter: andy dreyfuss
> Priority: Major
> Labels: queue, queued, task, tasks
> Attachments: Screen Shot 2018-06-08 at 3.37.25 PM.png
>
>
> I saw this issue originally on 1.9 stable, and am now running from the
> current master tip of the code, and the issue is still present. The image
> below shows our list of dags. Six tasks are actually underway, down from 16
> previously, and when those complete no more will be dequeued. If I attempt to
> trigger a new run it will immediately be queued.
>
> Can you please suggest any debugging steps I should take, workarounds, or
> fixes I can consider on my end?
>
> Thanks!
>
> !Screen Shot 2018-06-08 at 3.37.25 PM.png!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
