airflow-commits mailing list archives

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

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

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

Yes sorry I mentioned this on gitter. With master deadlock detection is broken due to the
eager creation. It will need the follow up patch from AIRFLOW-128.

> 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
>         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)

Mime
View raw message