You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Daniel Imberman (Jira)" <ji...@apache.org> on 2020/03/27 23:16:00 UTC

[jira] [Closed] (AIRFLOW-374) Kill task instances that haven't been able to heartbeat for a while

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

Daniel Imberman closed AIRFLOW-374.
-----------------------------------
    Resolution: Auto Closed

> Kill task instances that haven't been able to heartbeat for a while
> -------------------------------------------------------------------
>
>                 Key: AIRFLOW-374
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-374
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: operators
>            Reporter: Paul Yang
>            Assignee: Paul Yang
>            Priority: Major
>             Fix For: 1.8.0
>
>
> A task run by the LocalTaskJob periodically updates a timestamp to indicate that the task is still alive and running. If the task is unable to update this timestamp for a long time (for example, due to DB connection errors), the scheduler may reschedule the task to run again. In such a case, it's possible that two instances of the task are running. The task can monitor the time since last heartbeat and kill itself to prevent such cases.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)