-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rabbitmq has known issues, replace queue backend to resolve them #93
Comments
Newer versions of celery have a django backend! that would reduce complexity of deploying and of security group management potentially substantially! needs research. |
Misread documentation about this, django cannot be used for the queue, our best option is to replace with redis and hope it isn't as problematic. |
alternative: try out Huey, a less complex task dispatch python library. |
Okay, last straw, we managed to get two concurrent data processing tasks on the same user. this can only happen if rabbitmq is either not atomic, or if rabbitmq does its whole totally-unnacceptable silent dropping of api calls thing. Use of rabbitmq is now considered a bug, we are swapping to reddis as soon as I have dev time for it. |
I recommend watching this talk before committing to replacement of RabbitMQ: https://2023.djangocon.us/talks/mixing-reliability-with-celery-for-delicious-async-tasks/ |
aaaaand celery 5.4 has redis bugs. https://github.com/celery/celery/milestone/40 |
deploy now uses updated ubuntu, python version, but something changed in rabbitmq configuration so I need to work that out. |
keeping this open so that we update to 5.4 along with ubuntu 24.04.... |
Celery 5.4 is released, dogfooding on staging server (I've read release notes, no anticipated issues). |
The original reason for which I opened this is actually more frequent after a Sentry update. Fantastic. |
putting this issue on pause because I don't even know if redis will fix this. |
closing issue, there is no need to change from rabbitmq at this time even with the problems it seems to cause as there's no evidence that these are not actually just celery problems. |
Celery/Celery tasks are sometimes.... unsuccessful in connecting, the system emits an ampq connection error. The reason is unclear, but it appears to be a rabbitmq issue.
If this issue remains swap the system over to use reddis for the celery task queue backend.
The text was updated successfully, but these errors were encountered: