Redis-py client connection_pool release causes SystemExit and Celery beat to stop scheduling tasks #8944
keaton-dataprophet
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Version: Celery: 5.3.6, Redis-py 5.0.1 and 5.1.0b3
Platform: Python 3.11.0 on Ubuntu 22.04 / AWS.
Description:
I am using redis as the message broker for celery-beat. The celery beat scheduler will intermittently get into a state where the following exception is raised:
causing it to stop scheduling tasks but where the systemd service remains in an active state and the service does not restart. Below is a sample of the .service file
The celery-beat service has to be manually restarted in order for it to start scheduling tasks again.
This behaviour started around the time we updated redis-py from 3.5.2 to 5.0.1 and celery from 4.4.6 to 5.3.6
Beta Was this translation helpful? Give feedback.
All reactions