potiuk commented on issue #14896: URL: https://github.com/apache/airflow/issues/14896#issuecomment-1213108092
> Thanks for your response! Unfortunately, I believe the issue is related to how the Celery Worker itself handles concurrency, regardless of the daemonic flag on the worker command itself. Looking more in to it I think my choices are Yeah. This is actually quite likely. > 1. Monkey patch the third party lib to use billiards; or > 2. change Celery's concurrency [setting](https://docs.celeryq.dev/en/stable/userguide/workers.html#concurrency) to use something other than multiprocessing, like eventlet 3. You can also vendor-in the 3rd-party library and replace the use of mutliprocessing with billiard. -- 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]
