airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Davydov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-678) Task instances can double-trigger
Date Mon, 26 Dec 2016 01:49:58 GMT

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

Dan Davydov commented on AIRFLOW-678:
-------------------------------------

Yes, not sure why the JIRA didn't close, closing it manually.

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

Mime
View raw message