[rabbitmq-discuss] configure external data store(like database) for message durability in rabbitmq
Michael Klishin
michael at rabbitmq.com
Mon Sep 30 16:41:35 BST 2013
On sep 30, 2013, at 7:37 p.m., "PATAR, SAGAR" <sp345s at att.com> wrote:
> My assumption is when we have a file store for message durability and if one of the node goes down in the cluster the messages not been consumed yet must have been stored in that node file system and will stay till the node is back up ... those message will not be accessible by other active nodes in the cluster because the file store for that node is not accessible to other nodes....and the messages will be delayed ...
>
> I am not sure how this scenario is handled ...seems to be a common problem
Using mirrored queues or asynchronous replication (using Shovel or Federation plugins).
See
http://www.rabbitmq.com/distributed.html
http://www.rabbitmq.com/clustering.html
http://www.rabbitmq.com/ha.html
MK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130930/d67086af/attachment.pgp>
More information about the rabbitmq-discuss
mailing list