[rabbitmq-discuss] Configuring RabbitMQ to support change in hostname

[Kapil Goyal]

Matthias, Tim,

Thanks for your response.

> The real problem is that the mnesia schema contains for each table a
reference to the node(s) on which it has copies. So if the host name
changes and rabbit is restarted it will think that its tables still live
on the host with the > old hostname.

So, if I change the node-name to rabbit at localhost in the evn-config file,
RabbitMQ still won't be able to handle the change in hostname because of
the old hostname being in mnesia tables. Is this correct? I am trying to
understand how RabbitMQ uses the hostname stored in mnesia tables.

Thanks
Kapil

-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com
[mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Matthias
Radestock
Sent: Sunday, April 07, 2013 2:34 PM
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Configuring RabbitMQ to support change in
hostname

On 03/04/13 10:48, Tim Watson wrote:
> You cannot use 'rabbit at 987sdfkjhisd7f7d87sdf' to connect to other 
> Erlang nodes unless the part after the @ is actually the hostname.

Indeed.

> In addition to this, mnesia - Erlang's distributed database - insists 
> on creating its on-disk schema in a folder which is named 
> Mnesia.<node-name>, and we have no control over that.

Actually, that directory is configurable. The real problem is that the
mnesia schema contains for each table a reference to the node(s) on which
it has copies. So if the host name changes and rabbit is restarted it will
think that its tables still live on the host with the old hostname.

Matthias.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss