ArvidMartensRenson opened a new issue, #50185:
URL: https://github.com/apache/airflow/issues/50185

   ### Apache Airflow version
   
   3.0.0
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   I am running a few dags that can start multiple workflow triggers. When the 
amount of triggers is low, below 10 or so; all works fine but whenever it goes 
higher the trigger runner seems to get stuck. I traced it back to one of the 
dag_count calls on RuntimeTaskInstance getting stuck/taking too long which 
locks all the other triggers and the syncing of the trigger runner as the 
SUPERVISOR_COMMS object stays in its locked state. The triggers seems to be 
started at the same time.
   
   I already tried to solve the problem by introducing a timeout on the count 
calls but that made the trigger runner crash as the incoming messages are 
getting mixed up (response of a cancelled call finally getting through). Only 
solution I see right now is to perform API calls on the public endpoint for the 
dag count method calls.
   
   ### What you think should happen instead?
   
   _No response_
   
   ### How to reproduce
   
   Have more than twenty or so workflow triggers running started at the same, I 
suppose they poll states at about the same time.
   
   ### Operating System
   
   debian 11
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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