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 2016/12/10 01:34:58 UTC

[jira] [Updated] (AIRFLOW-679) Stop concurrent task instances from running due to race conditions

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

Alex Guziel updated AIRFLOW-679:
--------------------------------
    Description: 
Right now, multiple copies of the same task instance can run if someone clicks on the UI multiple times. To fix this, I propose two things:

1) record hostname and pid in TaskInstance table, then when heartbeating, only continue running if it matches

  was:
Right now, multiple copies of the same task instance can run if someone clicks on the UI multiple times. To fix this, I propose two things:

1) Use a transaction to set state to running, and don't run otherwise
2) record hostname and pid in TaskInstance table, then when heartbeating, only continue running if it matches


> Stop concurrent task instances from running due to race conditions
> ------------------------------------------------------------------
>
>                 Key: AIRFLOW-679
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-679
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Alex Guziel
>            Assignee: Alex Guziel
>            Priority: Minor
>
> Right now, multiple copies of the same task instance can run if someone clicks on the UI multiple times. To fix this, I propose two things:
> 1) record hostname and pid in TaskInstance table, then when heartbeating, only continue running if it matches



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