On 3/6/06, Jim Jagielski <[EMAIL PROTECTED]> wrote: > Garrett Rooney wrote: > > > > On 3/6/06, Jim Jagielski <[EMAIL PROTECTED]> wrote: > > > I think the whole issue revolves around whether the balancer > > > should, or should not, pre-open connections and manage them > > > internally, or whether it should be one-shot. The real > > > power is being able to load balance, and implement > > > that in a central location. > > > > > > So it seems to me that some sort of Balancer member > > > option that determines whether or not the connection > > > is "persistent" or not would alleviate some of > > > the issues you raise. > > > > We actually have a way to do that, it's the close_on_recycle flag, and > > I had to turn it on in order to get anything approaching reliability > > for fastcgi. > > > > That's how we do it *internally* and not what I meant. I meant > more a parameter to be set in httpd.conf...
Sure, we could add a parameter to control that behavior, but it still won't solve the real underlying problem, you'll still get collisions under load, they just won't be as common. -garrett
