airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-900) Double run job should not terminate the existing running job
Date Mon, 13 Mar 2017 02:50:05 GMT

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

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

Commit 1243ab16849ab9716b26aeba6a11ea3e9e9a81ca in incubator-airflow's branch refs/heads/v1-8-test
from [~saguziel]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=1243ab1 ]

[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
>             Fix For: 1.8.0
>
>
> 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)

Mime
View raw message