Nataneljpwd commented on issue #45636: URL: https://github.com/apache/airflow/issues/45636#issuecomment-2896644990
@cheery550 I think that the issue may still persist here, if you have a lot of tasks which are not ready to be running, however, are queued, the issue may still persist, in addition to the scheduler now being stuck in the critical section for longer (as it loops over the critical section). If we assume a dag with hundreds or thousands of tasks (could me mapped tasks), it is still possible to exit the loop after the proposed max iterations with less than 32 ti's set to running. If I did not fully understand the solution you proposed, I would be more than happy if you could provide a more profound explanation with examples. -- 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-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org