[ https://issues.apache.org/jira/browse/AIRFLOW-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301507#comment-15301507 ]
Bolke de Bruin edited comment on AIRFLOW-168 at 5/26/16 4:44 AM: ----------------------------------------------------------------- Yes sorry I mentioned this on gitter. With master deadlock detection is broken due to the eager creation and the scheduler will not check for existing task_instances before creation, hence the constraint error. It will need the follow up patch from AIRFLOW-128. Black is indeed the color (basically undefined) for tasksinstances that are created but have not been picked up by the scheduler. was (Author: bolke): 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. Black is indeed the color (basically undefined) > 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)