[
https://issues.apache.org/jira/browse/AIRFLOW-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16865675#comment-16865675
]
Fokko Driesprong commented on AIRFLOW-4586:
-------------------------------------------
Which executor are you running? The tasks in queue state are dispatched by the
scheduler and this means that all dependencies are met. In this case, you
should check if the tasks are being picked up by the workers. For example,
check if they are being consumed from the queue.
> Task getting stuck in Queued State
> ----------------------------------
>
> Key: AIRFLOW-4586
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4586
> Project: Apache Airflow
> Issue Type: Bug
> Components: scheduler
> Affects Versions: 1.10.0
> Reporter: raman
> Assignee: raman
> Priority: Major
>
> We are observing intermittently that Tasks get stuck in queued state and
> never get executed by Airflow. On debugging it we found that one of the
> queued dependency was not met due to which task did not move from queued to
> running state. So task remained in queued state. (are_dependencies_met
> function returned false for QUEUE_DEPS inside
> _check_and_change_state_before_execution).
> By looking into scheduler code it seems that scheduler does not reschedule
> the queued state tasks due to which task never got added to executor queue
> again and remained stuck in queued state. There is a logic inside
> _check_and_change_state_before_execution function to move the task from
> queued to None state(which gets picked by scheduler for rescheduling) if
> RUN_DEPS are not met but this logic seems to be missing for QUEUE_DEPS. It
> seems that task should be moved to None state even if QUEUE_DEPS are not met.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
