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

[GitBox <gi...@apache.org>]

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


   We've just migrated to `2.1.1` and are continuing to see tasks stuck in `Scheduled` using the `LocalExecutor`.
   
   In our case, Airflow seems to kick off tasks as expected until a DAG reaches it's concurrency limit (which we typically set at the individual DAG level instead of globally). Once a DAG hits the concurrency limit then tasks in other DAGs don't start executing despite Airflow having open executor slots. We're only making use of the `default_pool` and tasks are moving from `Queued` to `Running` there but aren't entering the queue despite being in a `Scheduled` state.


-- 
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