[
https://issues.apache.org/jira/browse/AIRFLOW-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506676#comment-16506676
]
andy dreyfuss commented on AIRFLOW-1143:
----------------------------------------
What's the best way to restart the scheduler? Send it a HUP? What about on OSX?
Is this issue the cause of https://issues.apache.org/jira/browse/AIRFLOW-2584
Thanks
> Tasks rejected by workers get stuck in QUEUED
> ---------------------------------------------
>
> Key: AIRFLOW-1143
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1143
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
> Reporter: Dan Davydov
> Assignee: Gerard Toonstra
> Priority: Major
>
> If the scheduler schedules a task that is sent to a worker that then rejects
> the task (e.g. because one of the dependencies of the tasks became bad, like
> the pool became full), the task will be stuck in the QUEUED state. We hit
> this trying to switch from invoking the scheduler "airflow scheduler -n 5" to
> just "airflow scheduler".
> Restarting the scheduler fixes this because it cleans up orphans, but we
> shouldn't have to restart the scheduler to fix these problems (the missing
> job heartbeats should make the scheduler requeue the task).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
