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

Bolke de Bruin commented on AIRFLOW-168:
----------------------------------------

I confirmed that this is actually also an issue on 1.7.1, but you will not see 
it:

{code}
mysql> select * from dag_run;
+----+--------------+---------------------+---------+---------------------------------------+------------------+------+----------+---------------------+
| id | dag_id       | execution_date      | state   | run_id                    
            | external_trigger | conf | end_date | start_date          |
+----+--------------+---------------------+---------+---------------------------------------+------------------+------+----------+---------------------+
|  1 | example_xcom | 2016-05-26 19:01:39 | running | 
scheduled__2016-05-26T19:01:39.071011 |                0 | NULL | NULL     | 
2016-05-26 19:01:39 |
|  2 | example_xcom | 2015-01-01 00:00:00 | running | 
scheduled__2015-01-01T00:00:00        |                0 | NULL | NULL     | 
2016-05-26 19:01:44 |
+----+--------------+---------------------+---------+---------------------------------------+------------------+------+----------+---------------------+
{code}

> schedule_interval @once scheduling dag atleast twice
> ----------------------------------------------------
>
>                 Key: AIRFLOW-168
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-168
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: Airflow 1.7.1.2
>            Reporter: Sumit Maheshwari
>            Assignee: Bolke de Bruin
>         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
(v6.3.4#6332)

Reply via email to