eladkal commented on PR #63583:
URL: https://github.com/apache/airflow/pull/63583#issuecomment-4062416004

   > Root Cause
   This addresses a known upstream Celery bug 
(https://github.com/celery/celery/issues/8030, 
https://github.com/celery/celery/issues/9054, 
https://github.com/celery/celery/issues/8990) where after a Redis broker 
restart, the worker reconnects at the transport level but fails to re-register 
its consumer on the queue. The worker process stays alive, celery inspect ping 
returns OK, but inspect.active_queues() returns None. Tasks pile up in the 
Redis queue and are never consumed.
   
   > The partial fix in https://github.com/celery/celery/pull/8796 did not 
fully resolve the issue, and it persists across Celery 5.2.x through 5.5.x with 
Redis broker.
   
   All reference issues are close ones. Do we have any open issue or a 
confirmation from Celery that this is an **open bug**?


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