Hi Team ,
We have a 2 node cluster with RMQ 3.13.1 and Erlang 26.2.2 .
We have by default, the vhost has quorum queues and around 5k pending messages in total all queues
Today , when we reboot one node , we see below behaviour :
1. Unable to publish message to cluster , on to a queue whose leader node is down . Ideally , cluster should take message and synchronize to both the nodes once all the nodes are up
2. We saw some message loss during the node restart , Is it general behaviour for a quorum queue to loose messages when node is restarted ?
3. How should we ensure High availability of messages / persistence even in case of node down in this version of RMQ and Quorum queues.
Thanks,
Abhishek
Hi,
start from using at least 3 nodes for your cluster https://www.rabbitmq.com/docs/clustering#node-count and see how it goes.
--
Best Regards,
Vilius
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
rabbitmq-user...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/rabbitmq-users/e63b225a-4fd5-41ad-ba95-2f5769198509n%40googlegroups.com.
WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enable macros.
To view this discussion visit https://groups.google.com/d/msgid/rabbitmq-users/5a7818cd-8f38-4ffe-9617-3ff0fdd914a2n%40googlegroups.com.