[rabbitmq-discuss] Cluster size limit
advaitalai at gmail.com
Wed Apr 20 18:54:30 BST 2011
I am clearing the /var/lib/rabbitmq/mnesia directory entirely before
starting the clustering process -- doesn't that ensure that any persistent
objects are cleared?
In any case, I will check the initial conditions of queues, exchanges etc.
and get back soon.
On Tue, Apr 19, 2011 at 4:27 PM, Matthew Sackman <matthew at rabbitmq.com>wrote:
> On Wed, Apr 06, 2011 at 09:39:40PM +0530, Advait Alai wrote:
> > >
> > > Hmm. What version of Erlang are you running? I get a slightly different
> > > error from the area of code I think is exploding...
> > >
> > I'm not very familiar with Erlang... 'erl -v' gives
> > Erlang R13B01 (erts-5.7.2)
> Hmm, that's a little old, but I'm not sure it should really be causing
> the issue you're seeing.
> You should essentially be doing:
> for node_to_add in $NODES; do \
> rabbitmqctl -n $node_to_add stop_app;
> rabbitmqctl -n $node_to_add reset;
> rabbitmqctl -n $node_to_add cluster $other_node $node_to_add;
> rabbitmqctl -n $node_to_add start_app;
> If that's what you're doing and it's not working, after the reset, have
> a poke around in that node's mnesia dir, and see if there's anything in
> there - there really shouldn't be - it should be empty. For some reason,
> the error you're getting is suggesting that on start_app, it's trying to
> recover a queue on the node newly added to the cluster, which turns out
> not to exist - this is hardly surprising - the reset will ensure there
> are no queues on that node. But I don't understand why it would be
> trying to do this.
> Try to make sure that you're starting with absolutely no queues or
> exchanges or anything configured in any node at all.
> As I say, it does work for me, so I'm not quite sure why it's going
> wrong for you.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss