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 Guziel (JIRA)" <ji...@apache.org> on 2017/09/06 20:51:00 UTC

[jira] [Resolved] (AIRFLOW-1493) Fix race condition with airflow run

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

Alex Guziel resolved AIRFLOW-1493.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

Issue resolved by pull request #2505
[https://github.com/apache/incubator-airflow/pull/2505]

> Fix race condition with airflow run
> -----------------------------------
>
>                 Key: AIRFLOW-1493
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1493
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Alex Guziel
>            Assignee: Alex Guziel
>             Fix For: 1.9.0
>
>
> Currently, airflow run spawns a process `airflow run --local` which spawns `airflow run --raw`.
> Local manages the heartbeat. Raw performs a series of checks, sets the state to running, runs the task, then sets the state to failed or success. 
> The problem is the heartbeat check on `airflow run --local` has to monitor the state in the DB, but because the change of state to running happens asynchronously, it must first observe the state in the DB to be running before it has the power of termination. However, there is no guarantee that it will observe this state. Thus, we should  move the pre-execution logic to airflow run --local



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)