[rabbitmq-discuss] Distributing Tasks to Worker Queues Across Federated Exchanges
stuff at moesel.net
Fri Dec 21 16:59:57 GMT 2012
Thanks for the reply, Tim. The nodes may be thousands of miles apart and
each geographic location will have its own cluster as well. We're trying
to find a solution that doesn't require any additional hardware and can be
configured somewhat easily via a GUI. A load balancer also would not
understand how to properly route based on queues/exchanges-- the key is
only to distribute/load-balance over the nodes that actually have consumers
for the given exchange/queue.
On Fri, Dec 21, 2012 at 11:12 AM, Tim Watson <tim at rabbitmq.com> wrote:
> On 21 Dec 2012, at 15:20, Chris wrote:
> > Hmmm... I just realized that the proposed configuration of setting
> things up in a ring will have one other adverse affect (besides weakening
> > If I have the ring setup like this: A --> B --> C --> A... then if B
> and C both have worker queues for the same type of task, B will tend to get
> too much preference because it will handle all requests from A and B (since
> the requests will never go to the AE to route to C)-- whereas the ideal
> setup would equally distribute requests from A to B and to C. Hmmm...
> It's probably possible to write a custom exchange type that co-operates
> with exchanges on other nodes to load balance, but there are likely to be
> all kinds of issues there. Why not just but a load balancer in front of
> four nodes?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss