Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kill task instances that haven't been able to heartbeat for a while #7925

Closed
dimberman opened this issue Mar 27, 2020 · 0 comments
Closed

Kill task instances that haven't been able to heartbeat for a while #7925

dimberman opened this issue Mar 27, 2020 · 0 comments
Labels
kind:bug This is a clearly a bug

Comments

@dimberman
Copy link
Contributor

dimberman commented Mar 27, 2020 •
edited

Description

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.

Use case / motivation

Related Issues

Moved here from https://issues.apache.org/jira/browse/AIRFLOW-374
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind:bug This is a clearly a bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dimberman @mik-laj