Hence the reason for the rewrite in 2.3/2.4. Balancer-manager in prev versions was NEVER intended for long-term usage. The issue is in the interaction of balancer-manager and mod_proxy_balancer, not the balancer itself. On Aug 4, 2011, at 10:57 AM, Tom Evans wrote: > On Thu, Aug 4, 2011 at 3:43 PM, Jim Jagielski <jim@xxxxxxxxxxx> wrote: >> You will note that the balancer in 2.3/2.4 resolves this issue. >> >> BTW, the idea that mod_proxy_balancer is "broken" only means that >> it does not do what you expect, which is restore all local mods >> made via balancer_manager, but this was never guaranteed. >> >> > > No, it applies state randomly and indiscriminately. The first time > this happened to us, one balancer cluster ended up with all backends > enabled, when only one was before the graceful restart, and yet > another had all backends disabled, when one should have been. > > IE, it left the balancer members in a state where it was neither the > configuration on disk, nor the configuration before restart. That is > what I call broken - an entirely unpredictable state. > > Given that load balancers are typically used to increase availability > and reliability of a web service, a load balancer which consistently > screws up the state is about as useful as an umbrella with holes in > it. > > Cheers > > Tom > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx > --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|