You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Alex Van Boxel (JIRA)" <ji...@apache.org> on 2016/12/25 13:54:58 UTC

[jira] [Updated] (AIRFLOW-678) Task instances can double-trigger

     [ https://issues.apache.org/jira/browse/AIRFLOW-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Van Boxel updated AIRFLOW-678:
-----------------------------------
    Component/s: core

> Task instances can double-trigger
> ---------------------------------
>
>                 Key: AIRFLOW-678
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-678
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: core
>            Reporter: Dan Davydov
>            Assignee: Dan Davydov
>
> At the moment there is no lock/synchronization around the loop where the scheduler puts tasks in the SCHEDULED state. This means that if somehow the task starts running or gets SCHEDULED somewhere else somehow (e.g. manually running a task via the webserver) the task can have it's state changed from RUNNING/QUEUED to SCHEDULED which can cause a single task instance to be run twice at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)