antontimenko commented on issue #14205: URL: https://github.com/apache/airflow/issues/14205#issuecomment-793231281
Of course, I can spend some time creating some kind of logic, that constantly makes requests to Airflow API to get the number of active DAG runs and trigger new ones only when there are less than 16 of them. But this would look like I'm trying to create some kind of my own scheduler on top of Airflow scheduler, just to get around this bug :) I think that scheduler should process any kind of DAG runs properly, even if there are more of them than `max_active_runs`. And as I said above, it worked properly in earlier versions ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
