JonnyWaffles commented on issue #14896:
URL: https://github.com/apache/airflow/issues/14896#issuecomment-1213100839

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


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