Thank you.<br><br><div class="gmail_quote">On Mon, Jun 17, 2013 at 3:18 AM, Tim Watson <span dir="ltr"><<a href="mailto:watson.timothy@gmail.com" target="_blank">watson.timothy@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 17 Jun 2013, at 05:24, Jason McIntosh <<a href="mailto:mcintoshj@gmail.com">mcintoshj@gmail.com</a>> wrote:<br>
<br>
> Queues exist (definition wise) on all nodes in a cluster. �Messages only existing unless the queue is mirrored on a single node.<br>
</div>[snip]<br>
<div class="im">> One reason you'd NOT have queues have their messages automatically replicated to other nodes is scaling. �If you had a cluster of 10 machines, and all the machines mirrored, then your message would have to hit all 10 nodes before being acknowledged<br>
<br>
</div>And to clarify, another reason why we have a consistent view of schema (I.e., definitions) is so that clients can connect to *any* node to interact with the queue.<br>
<div class="im"><br>
> Rabbit is also a Master-slave write system.<br>
> Only ONE node in a cluster is the "master".<br>
<br>
</div>Correction: rabbit HA is a master/slave system. Rabbit clustering is not and all nodes are considered equal.</blockquote></div><br>