[
https://issues.apache.org/jira/browse/AIRFLOW-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651685#comment-16651685
]
jack commented on AIRFLOW-374:
------------------------------
Not sure if this is related but on 1.9.0 I occasionally see DAG run and a teak
that is running but in fact the task is stuck. The operation takes less than 1
minute to be executed and the DAG was missing 2 days of executions! (on
weekend). When I clear the task it changes immediately to "up for retry" but
without my manual clear it would have stuck on running for ever. I would highly
appreciate a fix which can retry the task if it's on running but not actually
running.
> 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
(v7.6.3#76005)
