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

Move to rabbitmq as broker #1058

Open
madprime opened this issue May 29, 2019 · 2 comments
Open

Move to rabbitmq as broker #1058

madprime opened this issue May 29, 2019 · 2 comments
Labels
affects-devs Affects developers, deployment, and site admin annoyance

Comments

@madprime
Copy link
Member

Following on advice from @beaugunderson in slack, who finds that RabbitMQ is generally more robust as a message broker. It seems like Redis unreliability is likely behind the hacky solution taken here: #1054 (It would be better to fix the underlying problem!)

Also mentioned here arvkevi/openhumansimputer#38 RabbitMQ message broker + Redis results backend seems to be a common setup for celery, and that's what ended up working for @arvkevi.

@madprime
Copy link
Member Author

madprime commented Jul 9, 2019

@gedankenstuecke any comments on this? It's not high priority, but would be great to yes/no for the record. Thanks!

@madprime madprime added affects-devs Affects developers, deployment, and site admin enhancement labels Jul 9, 2019
@gedankenstuecke
Copy link
Member

Ah, yes! Agree on that switching would be good as Redis seems unreliable!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-devs Affects developers, deployment, and site admin annoyance
Projects
None yet
Development

No branches or pull requests

2 participants