You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/03/11 18:56:04 UTC

[jira] [Commented] (AIRFLOW-900) Double run job should not terminate the existing running job

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

ASF subversion and git services commented on AIRFLOW-900:
---------------------------------------------------------

Commit bb39078a35cf2bceea58d7831d7a2028c8ef849f in incubator-airflow's branch refs/heads/master from [~saguziel]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=bb39078 ]

[AIRFLOW-900] Fixes bugs in LocalTaskJob for double run protection

Right now, a second task instance being triggered
will cause
both itself and the original task to run because
the hostname
and pid fields are updated regardless if the task
is already running.
Also, pid field is not refreshed from db properly.
Also, we should
check against parent's pid.

Will be followed up by working tests.

Closes #2102 from saguziel/aguziel-fix-trigger-2


> Double run job should not terminate the existing running job
> ------------------------------------------------------------
>
>                 Key: AIRFLOW-900
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-900
>             Project: Apache Airflow
>          Issue Type: Sub-task
>            Reporter: Alex Guziel
>            Assignee: Alex Guziel
>
> Right now, jobs seem to get run an hour after they start and due to the logic, both get killed. Since we can't isolate the cause, we improve the logic here to only kill the new job.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)