[rabbitmq-discuss] RabbitMQ HA set up not working as expected

Wed Apr 23 17:50:26 BST 2014

Please consult the documentation on HA via mirrored queues at:

http://www.rabbitmq.com/ha.html

One wants to be careful about how one uses the term "high availability."
 Normally a queue will reside on only one node of a cluster, and its
availability will be subject to the health of that node.  HA via mirrored
queues allows you to specify that a queue or queues will be replicated on
more than one node of a cluster, thereby guarding against failure of what
would otherwise be a single node holding the queue.

So do you want to mirror all queues?  Maybe, but it depends on your actual
requirements.
HA via mirrored queues, as the above link explains, isn't a switch one
throws once on the cluster and walks away from, ticking off a box on one's
checklist marked "High Availability: Done."

If you want to guard against message loss in the presence of failures,
there are other things your applications will have to think about,
particularly around the transfer of responsibility for messages as they
pass in and out of the broker, whether by using a proper acknowledgement
discipline with consumers, using publisher confirms on the producer side,
or using transactions, and handling the various failure notifications that
can happen when a connection or cluster node go down, potentially
retransmitting on demand, being prepared to see a duplicated message under
certain failure syndromes, etc.  These issues are all discussed in the
above link.

Best regards,
Jerry

On Wed, Apr 23, 2014 at 9:43 AM, Anita Yip <Anita.Yip at realpage.com> wrote:

>   To achieve High Availability, I do need to mirror all the queues,
> right? Or is there any other way. My basic requirement is that when one
> Rabbit server goes down, the apps connecting to it should not get affected
> and the messages should not be lost.
>
>  *Anita Yip*
> RealPage, Inc.
> 360 Third Street   Suite 450
> San Francisco, CA  94107
>
>  Office:  415-395-2109
> Anita.yip at realpage.com <don.dalenberg at relapage.com>
> www.realpage.com
>
> *Connect with RealPage:*
>
> [image: Description: Description: Description:
> cid:image003.jpg at 01CE5184.4C0A9D20] <http://www.realpage.com/>[image:
> Description: Description: Description: cid:image005.gif at 01CE5184.4C0A9D20]<http://twitter.com/RealPage>
>  [image: Description: Description: Description:
> cid:image006.gif at 01CE5184.4C0A9D20] <http://www.facebook.com/RealPage> [image:
> Description: Description: Description: cid:image007.png at 01CE5184.4C0A9D20]<http://www.youtube.com/realpagemedia>
>  [image: Description: Description: Description:
> cid:image008.jpg at 01CE5184.4C0A9D20]<http://www.linkedin.com/company/realpage-inc.>
>  [image: Description: Description: Description:
> cid:image009.jpg at 01CE5184.4C0A9D20]<http://www.propertymanagementinsider.com/>
>
>
>   From: Jerry Kuch <jkuch at gopivotal.com>
>
> Reply-To: Discussions about RabbitMQ <rabbitmq-discuss at lists.rabbitmq.com>
> Date: Tuesday, April 22, 2014 4:08 PM
>
> To: Discussions about RabbitMQ <rabbitmq-discuss at lists.rabbitmq.com>
> Subject: Re: [rabbitmq-discuss] RabbitMQ HA set up not working as expected
>
>    On Tue, Apr 22, 2014 at 4:03 PM, Anita Yip <Anita.Yip at realpage.com>wrote:
>
>>   Ignore the below email, as it turned out the set up is not correct. On
>> a similar note, can you please let me know if high availability set up is
>> possible at a cluster level?
>>
>
>  In old Rabbits HA/mirroring is a property of the queue, granted to it
> when the queue is declared.
>
>  In newer Rabbits, HA is defined by a policy, which applies to a pattern
> specifying the names of the objects the policy is supposed to modify.  For
> details see here:  http://www.rabbitmq.com/ha.html
>
>  Are you sure you want to mirror absolutely all of the queues?
>
>
> ------------------------------
>
> This message is intended only for the use of the individual(s) or entity
> to which it is addressed and may contain information that is privileged,
> confidential, and/or proprietary to RealPage and its affiliated companies.
> If the reader of this message is not the intended recipient, you are hereby
> notified that any dissemination, distribution, forwarding or copying of
> this communication is prohibited without the express permission of the
> sender. If you have received this communication in error, please notify the
> sender immediately and delete the original message.
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140423/0f7cc098/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4AC7ACDF-CDB3-4930-A66C-481C9E292AE1[115].png
Type: image/png
Size: 1722 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140423/0f7cc098/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4CF393B6-2ADA-418D-AC2B-5D67FA784399[115].png
Type: image/png
Size: 1885 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140423/0f7cc098/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2AC40763-6D00-4A59-9A0C-A5525B44EC57[115].png
Type: image/png
Size: 1875 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140423/0f7cc098/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 91E364DD-5CE6-493B-8292-4DD276F2B5D4[115].png
Type: image/png
Size: 1254 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140423/0f7cc098/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 72716D1A-8A3D-46B6-A89B-999285564183[115].png
Type: image/png
Size: 4781 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140423/0f7cc098/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 00859B61-FDB7-4823-A9ED-23D3130E18AC[115].png
Type: image/png
Size: 1360 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140423/0f7cc098/attachment-0005.png>