[rabbitmq-discuss] High-availability: Unsynchronised mirrors questions (3.0.2)
vladislav.pernin at gmail.com
Wed Mar 13 11:11:57 GMT 2013
I'd like to hear more about these planned improvements ?
Will it be something like joining the cluster and filling in the queue with
existing messages to have a fully synchronised state ?
2013/3/13 Simon MacMullen <simon at rabbitmq.com>
> See http://www.rabbitmq.com/ha.**html#unsynchronised-slaves<http://www.rabbitmq.com/ha.html#unsynchronised-slaves>
> And note that we will be making improvements in this area in 3.1.
> Cheers, Simon
> On 13/03/13 10:53, Alexis Van Der Merwe wrote:
>> Hi there,
>> I'm testing out the HA features using server version 3.0.2 and it seems
>> to fulfill my requirements.
>> There's one thing I don't really understand, and I was hoping someone
>> would be able to enlighten me.
>> I have a two (2) node HA cluster, for convenience, let's call them
>> /NODE-MASTER/ and /NODE-SLAVE/.
>> 1. I publish 100k messages to NODE-MASTER, and they are replicated to
>> 2. I take down /NODE-MASTER/ using *rabbitmqctl*.
>> 3. NODE-SLAVE is promoted to master and retains the messages it
>> previously received.
>> 4. Bring /NODE-MASTER/ back up and into the cluster
>> This all works as I expect it to, but after the former master node
>> rejoins the cluster,
>> I see a message in the web-management console saying that one of the
>> nodes is unsynchronised (see screenshot).
>> Why does this occur, and more importantly, what does it mean in this
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
> Simon MacMullen
> RabbitMQ, VMware
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss