Hi Reka, I'm sorry for the confusion, this is how it works:
1. TopologyManager builds the topology data structure irrespective of the logic in the LoadBalancerTopologyReceiver. Which means TopologyManager has the complete topology model (Service -> Clusters -> Members) built after applying message filters. 2. We have used LoadBalancerTopologyReceiver to build the cluster maps in LoadBalancerContext. Here what we do is we store references to Cluster objects found in TopologyManager in LoadBalancerContext for faster access. 4. Since we use references to existing data model we do not need to copy the Members. They are automatically referenced. Does this answer your question? Thanks Imesh On Fri, Jan 17, 2014 at 4:31 AM, Reka Thirunavukkarasu <[email protected]>wrote: > Hi Imesh, > > Have we done $subject in the load balancher? Or are we adding the members > to load balancher in a different manner? > > As i checked the code > org.apache.stratos.load.balancer.LoadBalancerTopologyReceiver does add the > cluster to Load Balancher when the first member gets activated. After that > when a second or the next member gets activated, how will the load > balancher knows about the member in order to route the request to any of > the member in the cluster? > > Thanks, > Reka > > -- > Reka Thirunavukkarasu > Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > >
