Skip to content
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

Closed
biblicabeebli opened this issue Jan 8, 2020 · 13 comments
Closed
Assignees
Labels
Bug Sounds like a bug! enhancement in some way this would improve the experience of using or developing and maintaining Beiwe

Comments

@biblicabeebli
Copy link
Member

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.

@biblicabeebli biblicabeebli added the enhancement in some way this would improve the experience of using or developing and maintaining Beiwe label Jan 8, 2020
@biblicabeebli
Copy link
Member Author

Newer versions of celery have a django backend! that would reduce complexity of deploying and of security group management potentially substantially!

needs research.

@biblicabeebli biblicabeebli changed the title rabbitmq is having issues, looks like it is a known bug rabbitmq has known issues, replace queue backend to resolve them Aug 18, 2020
@biblicabeebli
Copy link
Member Author

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.

@biblicabeebli
Copy link
Member Author

alternative: try out Huey, a less complex task dispatch python library.
https://huey.readthedocs.io/en/latest/

@biblicabeebli biblicabeebli added the Bug Sounds like a bug! label Feb 21, 2022
@biblicabeebli
Copy link
Member Author

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.

@hackdna
Copy link
Member

hackdna commented Feb 20, 2024

I recommend watching this talk before committing to replacement of RabbitMQ: https://2023.djangocon.us/talks/mixing-reliability-with-celery-for-delicious-async-tasks/

@biblicabeebli
Copy link
Member Author

aaaaand celery 5.4 has redis bugs. https://github.com/celery/celery/milestone/40

@biblicabeebli
Copy link
Member Author

deploy now uses updated ubuntu, python version, but something changed in rabbitmq configuration so I need to work that out.

@biblicabeebli
Copy link
Member Author

keeping this open so that we update to 5.4 along with ubuntu 24.04....

@biblicabeebli
Copy link
Member Author

Celery 5.4 is released, dogfooding on staging server (I've read release notes, no anticipated issues).

@biblicabeebli
Copy link
Member Author

The original reason for which I opened this is actually more frequent after a Sentry update. Fantastic.

@biblicabeebli
Copy link
Member Author

putting this issue on pause because I don't even know if redis will fix this.

@biblicabeebli
Copy link
Member Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Sounds like a bug! enhancement in some way this would improve the experience of using or developing and maintaining Beiwe
Projects
None yet
Development

No branches or pull requests

2 participants