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

Kapil Goyal goyalk at vmware.com
Fri Mar 29 23:18:20 GMT 2013

Thanks Dushin. Setting NODENAME to rabbit at localhost in rabbitmq-env.conf
seems to work. But, if I were to later implement clustering/federation of
multiple such servers, each having rabbit at localhost as the node-name won't
work. I am thinking of solving it by replacing rabbit at localhost with
rabbit@<random string> before RabbitMQ starts for the first time. Does
<random string> have to be DNS resolvable?



From: rabbitmq-discuss-bounces at lists.rabbitmq.com
[mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Dushin
Sent: Thursday, March 28, 2013 6:44 PM
To: Discussions about RabbitMQ
Subject: Re: [rabbitmq-discuss] Configuring RabbitMQ to support change in







On Mar 28, 2013, at 4:53 PM, Kapil Goyal <goyalk at vmware.com> wrote:

RabbitMQ creates a new database if hostname is changed (as documented at
<http://www.rabbitmq.com/ec2.html> http://www.rabbitmq.com/ec2.html).


I need to support the hostname change on my RabbitMQ server without
impacting its functioning. Can I accomplish this by setting the NODENAME
environment variable in rabbitmq-env.conf. It seems from rabbitmq-server
script that names of database, logs etc. try to use this variable before
resorting to using hostname. Is this the right approach? Are there any
side-effects to look out for?



Kapil Goyal


VMware Inc.

rabbitmq-discuss mailing list
 <mailto:rabbitmq-discuss at lists.rabbitmq.com>
rabbitmq-discuss at lists.rabbitmq.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130329/88b3f6c9/attachment.htm>

More information about the rabbitmq-discuss mailing list