[GitHub] [airflow] fjmacagno commented on issue #20788: AIrflow Scheduler does not schedule any tasks when >max running tasks queued with non-existant pool

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

fjmacagno commented on issue #20788:
URL: https://github.com/apache/airflow/issues/20788#issuecomment-1010173998


   I mean, I just dont think the whole scheduler should stop scheduling tasks because one dag is misconfigured. This caused an entire cross-team airflow installation to stop working because one team made a mistake on one dag, and gods help us if that had been prod.
   
   It seems like if a task is misconfigured in some way that prevents it from running, it shouldn't be considered to be in the queue. Maybe it could at least be shoved to the back of the queue so that other tasks can try to run?


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