You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/02/04 07:23:21 UTC

[GitHub] [airflow] jpkoponen commented on issue #13542: Task stuck in "scheduled" or "queued" state, pool has all slots queued, nothing is executing

jpkoponen commented on issue #13542:
URL: https://github.com/apache/airflow/issues/13542#issuecomment-1029720475


   I have had the same issue happen randomly and I was forwarded here by AWS support. I am considering using the utility DAG posted by @danmactough above, but I would like to make it automatic. The idea is to make it a periodic DAG that would go through all the DAGs, e.g. once per hour, and find the tasks that are stuck if there are any. I would suppose that it is possible somehow. However, I am afraid that the utility DAG itself would take too much resources and block other tasks. Do you @danmactough have any intuition if this is an applicable idea and why did you choose to make the DAG be triggered manually instead of automatic?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org