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

Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2016/06/27 16:52:52 UTC

[jira] [Closed] (AIRFLOW-279) Dagrun timeouts not applied after max number of active runs is reached

     [ https://issues.apache.org/jira/browse/AIRFLOW-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini closed AIRFLOW-279.
-----------------------------------
    Resolution: Duplicate

Dupe according to the PR.

> Dagrun timeouts not applied after max number of active runs is reached
> ----------------------------------------------------------------------
>
>                 Key: AIRFLOW-279
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-279
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: Airflow 1.7.1.3
>            Reporter: Betsy Cannon
>            Assignee: Betsy Cannon
>            Priority: Minor
>
> `schedule_dag` checks against the max number of active runs and exits early before cleaning up dagruns that have timed out. This means if you reach the max number of runs, the timeouts are never applied and new dagruns are not started. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)