On 04/14/2006 02:17 PM, Mladen Turk wrote: > Ruediger Pluem wrote: > >> >> Does anybody remember why we are making a copy of the worker? > > > Usually a worker represents a backend appserver instance. > Now you can have multiple load balancers with different > lb factors for the same set of workers, > but for the different application mappings. > > Lets say that you have workers w1, w2, w3, and load balancers b1 and > b2. Both b1 and b2 have the same set of workers w1-w3, but with the > different lb factors for each worker, so that for b1 its: 1:1:2 > and for the b2 it's 2:2:1, etc.
So that would be something like: <Proxy balancer://b1> BalancerMember http://w1 loadfactor=1 BalancerMember htpp://w2 loadfactor=1 BalancerMember htpp://w3 loadfactor=2 </Proxy> <Proxy balancer://b2> BalancerMember http://w1 loadfactor=2 BalancerMember htpp://w2 loadfactor=2 BalancerMember htpp://w3 loadfactor=1 </Proxy> > > This allows to have common worker parameters like error status > shared across multiple balancers, while maintaining per-balancer > worker data. Ok, I understand these goals, but as far as I can see from the current code they do not share the error status as they are using different scoreboard slots and thus w1 from b1 is using a different proxy_worker_stat then w1 from b2. Regards Rüdiger
