[rabbitmq-discuss] Incorrect display of mirrored queues as unsynchronised after database failover

[Matt Pietrek]

Back before 2.8.0 was announced, I reported an issue with Mirrored queues
reporting some nodes as unsynchronized.  SimonM says it was fixed, per the
release notes:

- fix incorrect display of mirrored queues as unsynchronised after database
  failover


However, I'm still seeing the issue in 2.8.2. In our cluster with several
mirrored queues in a three-node cluster, I do a "rolling upgrade" operation
wherein I restart each node in sequence. After bring each node back up I
wait for the queue to become fully synchronized before moving on to the
next node.

At the beginning of the rolling restart, the queue has no messages in it
and the management UI says there are two synchronized nodes in addition to
the master.

At some later point after restarting a node, the management console and
HTTP API report that one of the nodes is unsynchronized, despite there
being 0 messages in the queue.

I have verbose mnesia tracing enabled if this would help track down the
problem.

Thanks,

Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120620/35e9c4f6/attachment.htm>