I am in the process of trying to setup a network of brokers for HA behind a load balancer. The aim is to allow clients to see a virtual broker (which is really load balanced and with fail over) with a single IP/port. The LBR is round robin spraying connections to all the masters and the slaves are there known only to other masters for draining messages if the master fails.
Here's an image of the conceptual architecture. http://www.nabble.com/file/p11219295/ActiveMQCluster.jpg Comments/suggestions/alternatives? If this is feasible what does this mean for durable subscribes as I forsee producers/consumers connecting to any broker. Has anyone tried such an architecture? Any alternative ways to achieve HA/scalability which shields the client from configuration changes as we scale up? I am attaching a preliminary config files for this setup (network only, no master/slave yet) http://www.nabble.com/file/p11219295/activemq.xml server1.xml , http://www.nabble.com/file/p11219295/activemq.xml server2.xml and http://www.nabble.com/file/p11219295/activemq.xml server3.xml -- View this message in context: http://www.nabble.com/How-to-have-a-highly-available-and-scalable-setup-using-network-of-brokers--tf3954224s2354.html#a11219295 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
