airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bolke de Bruin (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-168) schedule_interval @once scheduling dag atleast twice
Date Thu, 26 May 2016 07:20:14 GMT


Bolke de Bruin commented on AIRFLOW-168:

The issue with double dagruns is due to this line:

            # don't ever schedule prior to the dag's start_date
            if dag.start_date:
                next_run_date = dag.start_date if not next_run_date else max(next_run_date,

which doesn't check if it was scheduled before. Will have a fix shortly.

> schedule_interval @once scheduling dag atleast twice
> ----------------------------------------------------
>                 Key: AIRFLOW-168
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: Airflow
>            Reporter: Sumit Maheshwari
>         Attachments: Screen Shot 2016-05-24 at 9.51.50 PM.png, screenshot-1.png
> I was looking at example_xcom example and found that it got scheduled twice. Ones at
the start_time and ones at the current time. To be correct I tried multiple times (by reloading
db) and its same. 
> I am on airflow master, using sequential executor with sqlite3. Though it works as expected
on a prod env which is running v1.7 with celery workers and mysql backend.  

This message was sent by Atlassian JIRA

View raw message