On Sat, Oct 25, 2014 at 2:19 PM, Nirmal Fernando <[email protected]> wrote:
> > > On Sat, Oct 25, 2014 at 6:26 AM, Imesh Gunaratne <[email protected]> wrote: > >> Hi, >> >> We have now fixed the following issues identified with the load balancer: >> >> - Fixed messaging component dependencies in load balancer package. >> - Fixed an issue in messaging component which raised a class cast >> exception in debug mode. >> - Added generated service host port to the member port map. This will >> overwrite the port value given by the cartridge definition with the >> generated service host port, if the cluster is kubernetes. >> - Now the load balancer will apply the load balancing algorithm on the >> list of members found in the cluster, not on the list of service proxies. >> > > Can you explain this a bit more please? Does this mean we are not going to > use Kubernetes service proxies anymore? > Yes, I also unclear on this. If we are not taking kubernetes service proxies, how do we identified members? > > >> We could improve further in a future milestone. >> >> Thanks >> >> -- >> Imesh Gunaratne >> >> Technical Lead, WSO2 >> Committer & PMC Member, Apache Stratos >> > > > > -- > Best Regards, > Nirmal > > Nirmal Fernando. > PPMC Member & Committer of Apache Stratos, > Senior Software Engineer, WSO2 Inc. > > Blog: http://nirmalfdo.blogspot.com/ > -- Lakmal Warusawithana Vice President, Apache Stratos Director - Cloud Architecture; WSO2 Inc. Mobile : +94714289692 Blog : http://lakmalsview.blogspot.com/
