[rabbitmq-discuss] Question about initial cluster connect & client-side cluster awareness

Matthias Radestock matthias at lshift.net
Thu Sep 18 20:08:30 BST 2008


Dmitriy Samovskiy wrote:
> All in all, I personally found the best approach is not to rely on known_hosts at all, and 
> tell each client (individually or as a group) IP addresses how they can connect to rabbit. 
> I also found connection.redirect response to be useless in this scenario, so I always set 
> insist to true when opening a connection. For load balancing, I use tcp level things like 
> haproxy instead of AMQP-level techniques. My clients each implement reconnect logic 
> individually.

Makes sense.

> Please note that known_hosts issues I described above are not specific to RabbitMQ. This 
> is just the way AMQP (0-8 at least) is - it provides means for cluster node discovery 
> after initial bootstrap only if all your clients are in the same network address space and 
> have access to the same name resolution services. AMQP experts - I would love to hear your 
> opinion on this one.

The clustering support that is part of the AMQP 0-8/9 protocol is really 
rudimentary and underspecified. And the draft 0.91 spec removes it 
completely. RabbitMQ will continue to cluster, and, as you suggest 
above, the existing techniques and techniques to make that transparent 
to the client should work well.



More information about the rabbitmq-discuss mailing list