You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: