gopidesupavan commented on issue #50185:
URL: https://github.com/apache/airflow/issues/50185#issuecomment-2917851474
@x42005e1f Really appreciate your thoughts here and all the suggestions :)
Yes, I agree, having an async version would be a good way to avoid all
these patches. If I remember correctly, the lock was introduced primarily to
prevent mixing API communication messages with triggerer workloads.
@kaxil @ashb It seems to me that having a separate channel for triggerer
workloads and API communication would be ideal in this scenario to avoid
deadlocks IMHO. Alternatively, implementing async versions of all relevant
methods could also work. Or, as @x42005e1f suggested, we could adopt the method
he mentioned—but as he noted, we’ll need to closely monitor its
coroutine-safety.
--
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]
