potiuk commented on issue #43180:
URL: https://github.com/apache/airflow/issues/43180#issuecomment-3538842937

   > I noticed that when a task is configured to use a pool that doesn't exist 
- tasks get stuck indefinitely with no indication of why.
   
   I don't think we even have place for logs for that - because essentially 
what happens is scheduler runs a join with `pool` table and this is how it 
selects tasks to run - so if you want to fix this one @Dev-iL , this is a new 
feature to add rather than logging - figure out a place somewhere where pool_id 
for tasks is checked against pool table.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to