[rabbitmq-discuss] Clustering issue

Valentin Bernard vbernard42 at gmail.com
Tue Apr 19 16:28:57 BST 2011


The version of RabbitMQ is the latest, but one of our nodes was hosted
on a Ubuntu server - with the packaged version of Erlang, which is
outdated (R13B03). Now that we excluded that node, the cluster doesn't
seem to become inconsistent anymore when running the previous tests.
Maybe the problem was there...

Thanks for your answer.


On 19 avr, 15:38, Matthew Sackman <matt... at rabbitmq.com> wrote:
> On Tue, Apr 19, 2011 at 06:16:24AM -0700, Valentin Bernard wrote:
> > ... and at the same time, we get a few inconsistent_database/
> > running_partitioned_network errors in the logs. If, while the cluster
> > was partitioned, we added or deleted some queues/exchanges, the nodes
> > indeed aren't synchronized, and even though they consider being in the
> > same cluster (and are able to communicate between each other), they
> > aren't aware of the same entities. No node were reseted during the
> > whole process. Is that a bug? This really isn't a problem for us, but
> > that's still somewhat disturbing – if the mnesia database is
> > inconsistent, the cluster should probably remain partitioned ;)
> Absolutely agreed - it should remain partitioned - the start_app should
> have failed. Could you check to make sure this issue occurs with the
> latest release - 2.4.1 if that's not what you're already running.
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list