<div dir="ltr">The notion of mirroring exchanges doesn't make sense.<div><br></div><div>An exchange is essentially metadata, shared across the cluster in a distributed database. There's no living, running entity beyond that backing it, and the routing work implied by the exchange is done by the process associated with the publishing channel.</div>
<div><br></div><div>A queue however is backed by a single Erlang process. A mirrored queue gains extra backing processes to support its mirrors. These processes must coordinate amongst themselves to make sure the same operations applied to the master are applied to the queues in the same order, so that a slave can be promoted to take over for its failed master.</div>
<div><br></div><div>You configure mirrored queues in recent Rabbit versions by creating a policy that names the queues you want to have mirrored and specifies the details for how they're mirrored (number of replicas, locations of replicas, etc.). In older versions you configured mirrored queues at queue.declare time, which was less flexible in a number of respects.</div>
<div><br></div><div>Best regards,</div><div>Jerry</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 4, 2013 at 10:15 AM, PATAR, SAGAR <span dir="ltr"><<a href="mailto:sp345s@att.com" target="_blank">sp345s@att.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I mean in Master/Slave architecture during the failovers ...<br>
<br>
If all exchanges are mirrored then we need to configure the exchanges which needs to be mirrored in Master/Slave .. Is that correct??<br>
<div class="im HOEnZb"><br>
-----Original Message-----<br>
From: <a href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com">rabbitmq-discuss-bounces@lists.rabbitmq.com</a> [mailto:<a href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com">rabbitmq-discuss-bounces@lists.rabbitmq.com</a>] On Behalf Of Michael Klishin<br>
</div><div class="im HOEnZb">Sent: Friday, October 04, 2013 1:06 PM<br>
To: Discussions about RabbitMQ<br>
Subject: Re: [rabbitmq-discuss] mirrored queue cluster<br>
<br>
<br>
</div><div class="HOEnZb"><div class="h5">On oct 4, 2013, at 9:01 p.m., "PATAR, SAGAR" <<a href="mailto:sp345s@att.com">sp345s@att.com</a>> wrote:<br>
<br>
> Thank you .. Apart from Queue.. We should be able to mirror a topic (I mean Topic Exchange) as well right.<br>
<br>
All exchanges are always mirrored. They are not really separate entities, just a distributed routing<br>
table that all nodes have a copy of. That's why you can publish to any node.<br>
<br>
MK<br>
<br>
<br>
<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>