You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "George Leslie-Waksman (JIRA)" <ji...@apache.org> on 2017/12/15 00:44:00 UTC

[jira] [Commented] (AIRFLOW-790) DagRuns do not exist for certain tasks, but don’t get fixed

    [ https://issues.apache.org/jira/browse/AIRFLOW-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291847#comment-16291847 ] 

George Leslie-Waksman commented on AIRFLOW-790:
-----------------------------------------------

We have also been seeing this issue.

It additionally causes problems for us because some dags will hit their concurrency limit but, since there's no DagRun, the TaskInstances will never be found and removed causing things to deadlock until we manually remove the task instances.

> DagRuns do not exist for certain tasks, but don’t get fixed
> -----------------------------------------------------------
>
>                 Key: AIRFLOW-790
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-790
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Bolke de Bruin
>
> Log gets flooded without a suggestion what to do



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)