Dynamic Message Queue Switching Fails When Using SocketIO.init_app() for Redis and RabbitMQ #2117
Unanswered
pratikbelote104896
asked this question in
Q&A
Replies: 1 comment
-
Switching the message queue for a server that is active is not supported. If you need this to work, I recommend you implement your own |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am facing an issue with Flask-SocketIO while trying to dynamically switch between Redis and RabbitMQ as message queues.
Environment:
Deployment: Gunicorn with Nginx.
Message Queues: Redis and RabbitMQ.
Scenarios:
Expected Behavior
When the system dynamically switches between Redis and RabbitMQ as message queues (using SocketIO.init_app()), the socket communication should work seamlessly regardless of the current message queue.
Observed Behavior
Code to Reproduce
init.py
main.py
nginx.conf
nginx.conf
Steps to Reproduce
Debug Information
Logs when Redis fails and switches to RabbitMQ:
Logs when Redis comes back online:
Request for Help
Please confirm if this is a bug or if there’s a workaround to ensure seamless switching of message queues in real-time.
Thank you for your support!
git_issue_raise.txt
Beta Was this translation helpful? Give feedback.
All reactions