<div dir="ltr">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.<div>
<br></div><div style>Thanks,</div><div style>Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Dec 21, 2012 at 11:12 AM, Tim Watson <span dir="ltr"><<a href="mailto:tim@rabbitmq.com" target="_blank">tim@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On 21 Dec 2012, at 15:20, Chris wrote:<br>
<br>
> Hmmm... I just realized that the proposed configuration of setting things up in a ring will have one other adverse affect (besides weakening HA).<br>
><br>
> 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...<br>
><br>
<br>
</div>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?<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br></div>