<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Following on to an earlier thread (<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2012-January/017146.html">http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2012-January/017146.html</a>) (Thanks Simon!), I've found something interesting.</div><div><br></div><div>I've modified my tool code to call rabbitmqadmin.py "list queues" using "slave_nodes" and "synchronised_slave_nodes" as suggested by SimonM, and it mostly works as expected. (I'm using raw_json as output, for what it's worth.)</div><div><br></div><div>In one case (the "VMMunger" queue below), the returned 'slave_nodes' field is empty, while the 'synchronised_slave_nodes' field is 'rabbit@play2'. In other words, exactly the *opposite* of what you'd expect if the queue was not in sync. The strangeness is further corroborated by the copy/paste results of the Queues tab in the Web management UI, which reports that the VMMunger queue *is* in sync:</div><div><br></div><div><a href="http://192.168.78.50:55672/#/queues/%2F/ConfigurationManager">ConfigurationManager</a>
rabbit@play
<acronym title="Synchronised mirrors: rabbit@play2">+1</acronym>
<acronym title="x-ha-policy: all">HA</acronym> <acronym title="durable: true">D</acronym>
<acronym title="Idle since 2012-1-24 11:40:31">Idle</acronym>
0
0
0</div><div><a href="http://192.168.78.50:55672/#/queues/%2F/VMMunger">VMMunger</a>
rabbit@play
<acronym title="Synchronised mirrors: rabbit@play2">+1</acronym>
<acronym title="x-ha-policy: all">HA</acronym> <acronym title="durable: true">D</acronym>
<acronym title="Idle since 2012-1-24 11:55:24">Idle</acronym>
0
0
0</div><div><a href="http://192.168.78.50:55672/#/queues/%2F/fake_configmgr">fake_configmgr</a>
rabbit@play
<acronym title="Synchronised mirrors: rabbit@play2">+1</acronym>
<acronym title="x-ha-policy: all">HA</acronym> <acronym title="durable: true">D</acronym>
<acronym title="Idle since 2012-1-24 11:40:31">Idle</acronym>
0
0
0</div><div><a href="http://192.168.78.50:55672/#/queues/%2F/fake_munger_queue">fake_munger_queue</a>
rabbit@play
<acronym title="Synchronised mirrors: rabbit@play2">+1</acronym>
<acronym title="x-ha-policy: all">HA</acronym> <acronym title="durable: true">D</acronym>
<acronym title="Idle since 2012-1-24 11:40:33">Idle</acronym>
0
0
0</div><div><a href="http://192.168.78.50:55672/#/queues/%2F/fake_service_2">fake_service_2</a>
rabbit@play
<acronym title="Synchronised mirrors: rabbit@play2">+1</acronym>
<acronym title="x-ha-policy: all">HA</acronym> <acronym title="durable: true">D</acronym>
<acronym title="Idle since 2012-1-24 11:40:31">Idle</acronym>
0
0
0 </div><div><br></div><div>The 'slave_nodes' and 'synchronised_slave_nodes' fields of the four other queues as returned by "list queues" are exactly what I'd expect them to be, and match up with the Web Mgmt UI.</div><div><br></div><div>Here's the returned JSON string, FWIW.</div><div><br></div><div><div>str: [</div><div>{"synchronised_slave_nodes":["rabbit@play2"],"messages":0,"slave_nodes":["rabbit@play2"],"name":" ConfigurationManager"},</div><div>{"synchronised_slave_nodes":["rabbit@play2"],"messages":0,"slave_nodes":[]," name":"VMMunger"},</div><div>{"synchronised_slave_nodes":["rabbit@play2"],"messages":0,"slave_nodes": ["rabbit@play2"],"name":"fake_configmgr"},</div><div>{"synchronised_slave_nodes":["rabbit@play2"],"messages":0," slave_nodes":["rabbit@play2"],"name":"fake_munger_queue"},</div><div>{"synchronised_slave_nodes": ["rabbit@play2"],"messages":0,"slave_nodes":["rabbit@play2"],"name":"fake_service_2"}</div><div>]</div></div><div><br></div><div>Any ideas?</div><div><br></div><div>Thanks much,</div><div><br></div><div>Matt</div></body></html>