[rabbitmq-discuss] Good practice to work with rabbit cluster?
carl.hoerberg at gmail.com
Mon Mar 12 12:20:32 GMT 2012
what about a multi A DNS record (with low ttl), which you update when
a server is down/up?
On Mon, Mar 12, 2012 at 11:26, stone <zmstone at gmail.com> wrote:
> Hi there!
> Is there any good practice regarding how to write self-managed AMQP client
> (Erlang based)
> Here is what I need to accomplish:
> 1. I don't what to hard-code hostname/ip address of rabbit-server,
> using a configuration file would be a simple solution, but, is there a
> better way?
> 2. Client should be able to get the rabbit server "running cluster"
> so if the current connection is broken, it could try another one in the
> then perhaps update the "running cluster" list from the new node;
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss