[rabbitmq-discuss] Good practice to work with rabbit cluster?

[Jerry Kuch]

This is also a pretty natural thing to do with a system like Zookeeper
from the Hadoop project, although it would require Rabbit to grow something
like a plugin that either had an Erlang Zookeeper client, or used a port
or jinterface to the native C or Java Zookeeper clients, to do the necessary
work...

Best regards,
Jerry

----- Original Message -----
From: "stone" <zmstone at gmail.com>
To: "Carl Hörberg" <carl.hoerberg at gmail.com>
Cc: rabbitmq-discuss at lists.rabbitmq.com
Sent: Monday, March 12, 2012 5:46:34 AM
Subject: Re: [rabbitmq-discuss] Good practice to work with rabbit cluster?


seems better than config file. thanks Carl.


2012/3/12 Carl Hörberg < carl.hoerberg at gmail.com >


no, you have to manually administer the dns (or automatically through
some heartbeat stuff interacting with your dns provider api.. )

i don't know how the client implementations are, but they could try to
connect to the first A record, if that fails try the next one and so
forth.. (like the way many web browsers does)



On Mon, Mar 12, 2012 at 13:28, stone < zmstone at gmail.com > wrote:
> I'm not sure how DNS server works, is it possible for the DNS server to
> detect the failure of a specific port? i.e. to find out if rabbit is down,
> when the OS is still up and running.
>
>
> 2012/3/12 Carl Hörberg < carl.hoerberg at gmail.com >
>>
>> 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"
>> > information.
>> > so if the current connection is broken, it could try another one in the
>> > cluster,
>> > then perhaps update the "running cluster" list from the new node;
>> >
>> > Brs
>> > /stone
>> >
>> >
>> > _______________________________________________
>> > rabbitmq-discuss mailing list
>> > rabbitmq-discuss at lists.rabbitmq.com
>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> >
>
>


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