Hi Sidath, On Fri, Aug 19, 2016 at 10:10 AM, Sidath Weerasinghe <[email protected]> wrote:
> Hi all, > > > In MB, the user/developers having to manually list out the IPs in the > connection URL could be difficult. The change of IPs of the broker nodes > would require reconfiguring and restart the client applications connected > to it. I am implementing a way to dynamically discover the MB nodes in the > cluster and load balance through them. > > > Via calling an admin service can discover MB nodes in the cluster > Periodically calling this service we can get the dynamically adding MB node > IP addresses and can remove disconnected IP addresses from the list. > > According to the live MB node IP address, I will create the connections > and use this connection as round robin fashion or use disruptor. > > > > There are several ideas for doing this. > > 1. Build separate OSGI component > 2. Modify the Andes client according to the above scenario. > Can you explain a bit more about how you are planning to expose the live MB IPs using these two methods? If the client needs to auto-discover live MB nodes, AFAIU we can expose a rest API from the MB node, which will return the current IP list for the MB cluster. WDYT? > > > Any ideas? > > > > > -- > Thank You, > Best Regards, > > Sidath Weerasinghe > > > *Intern* > > *WSO2, Inc. * > > *lean . enterprise . middleware * > > > *Mobile: +94719802550 <%2B94%20777764144>* > > *Email: *[email protected] <[email protected]> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Thanks and Regards, Isuru H. +94 716 358 048* <http://wso2.com/>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
