[jira] [Comment Edited] (AIRFLOW-39) DagRun scheduled after end_date

["Siddharth Anand (JIRA)" <ji...@apache.org>]

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

Siddharth Anand edited comment on AIRFLOW-39 at 5/5/16 1:04 AM:
----------------------------------------------------------------

Ok, I reproduced this on 1.7.0 and on head master. 

The handling is a little different on both. In both cases, DAG runs keep getting inserted beyond the end_date -- that is a bug and causes needless amount of work. 

In 1.7.0, the runs past the end_date are left in a RUNNING state, whereas in head master, the runs past the end_date are "failed".




was (Author: sanand):
Ok, I reproduced this on 1.7.0 and will try to reproduce on master head as well. Thanks for reporting this and bringing it to our attention. 




> DagRun scheduled after end_date
> -------------------------------
>
>                 Key: AIRFLOW-39
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-39
>             Project: Apache Airflow
>          Issue Type: Wish
>    Affects Versions: Airflow 1.7.0
>         Environment: -  Airflow version: v1.7.0
> -  Airflow components: webserver and scheduler with a postgres database and LocalExecutor
> -  Python Version: 2.7.9
>            Reporter: dud
>            Assignee: Siddharth Anand
>            Priority: Minor
>         Attachments: tutorial4.png, tutorial4_grpah.png
>
>
> Hello
> When I write a new DAG, it is automatically picked by the scheduler as intended. However the end_date parameter is not accounted when creating a DagRun, so that DagRuns scheduled after end_date are being displayed in the web interface and are staying in the running state forever as the scheduler doesn't launch them.
> From my reading of the sources, the end_date paremeter is not used when creating a DagRun.
> Is there any reason for this behaviour ?
> Regards
> dud



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