<html><head></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>I'm experiencing a problem with mirrored queue synchronization, and I'm trying to determine if there's a bug or I'm just not understanding something.</div><div><br></div><div>Our setup:</div><ul><li>RabbitMQ 2.71 on 64-bit Ubuntu 10.04.</li><li>Three brokers with all queues mirrored</li><li>Web Management plugin installed</li></ul><div><br></div><div>We typically have five queues defined, all mirrored. If I observe them in the "Queues tab" of the Management UI, they all have a green "+2" after the Node name. They're all mastered on the same Node.</div><div><br></div><div>None of these queues have any messages, and there are no clients connected, sending or receiving messages.</div><div><br></div><div>If I stop one of the brokers, all the "+2"s become "+1", as expected. However, when I restart the broker a couple of seconds later, some subset of the queues (varies from run to run) go back to "+2", while the remaining queues switch to "+1 +1", meaning 1 synched, and 1 unsynched.</div><div><br></div><div>Given that there are no messages in the queue, I don't understand why some queues don't synch back up properly.</div><div><br></div><div>Also, I've looked at the sync status of the queues in rabbitmqctl, and the results seem consistent with what the HTTP API reports.</div><div><br></div><div>Matt</div><div><br></div></body></html>