Thanks, Emile.<br><div><br></div><div>I ran the command and here's what I see -�<a href="https://dl.dropboxusercontent.com/u/162706/list_queues.png">https://dl.dropboxusercontent.com/u/162706/list_queues.png</a></div><div>
<br></div><div>I was expecting to see the name of the queues and the master node listed next to it. That's not quite what I see on the screen though.</div><div><br></div><div>Also, does a master node in this case refer to the node the queue was created on? And if yes, does this mean if there are multiple queues in an HA cluster (each created on a different node), there could multiple masters at any given time in a mirrored queue set up?</div>
<div><br><div class="gmail_quote">On Tue, Jul 16, 2013 at 6:26 AM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com" target="_blank">emile@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
<div><div class="h5"><br>
On 15/07/13 22:19, Girish Gangadharan wrote:<br>
<br>
> Can somebody please explain to me how does one go about identifying the<br>
> slave vs master nodes in a cluster? The idea is to bring one down and<br>
> see how the clients handle them, especially the Consumer Cancellation<br>
> notifications (for testing high availability setup). Also, is that a<br>
> valid way to test HA? Or the fact that these nodes sit behind a<br>
> load-balancer make it an unnecessary, redundant test?<br>
<br>
</div></div>There is no unique master node in a cluster, since the concept of master<br>
is defined per HA queue. You can determine the master node for each<br>
queue with "rabbitmqctl list_queues pid"<br>
<br>
Stopping the master node of a queue sounds like a valid test regardless<br>
of load-balancer.<br>
<span class="HOEnZb"><font color="#888888"><br>
<br>
-Emile<br>
<br>
<br>
<br>
<br>
</font></span></blockquote></div><br></div>