airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Riccomini (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-39) DagRun scheduled after end_date
Date Thu, 05 May 2016 14:40:12 GMT

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

Chris Riccomini commented on AIRFLOW-39:
----------------------------------------

+1

> 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: 1_7_0_dag_runs_past_date_running.png, Head_master_dag_runs_past_date_failed.png,
Jobs_view_only_shows_runs_within_start_end_range.png, Task_instance_view_only_shows_TIs_within_start_end_range.png,
Tree_view_only_shows_runs_within_start_end_range.png, 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)

Mime
View raw message