Hi Dave, On Tue, Sep 30, 2008 at 6:13 PM, Dave Dykstra <dwd@xxxxxxxx> wrote: > I found out a little bit more by looking in the source code and the > generated headers and setting a few breakpoints. The squid closest to > the origin server that is down (the one at the top of the cache_peer > parent hierarchy) never attempts to store the negative result. Worse, > it sets an Expires: header that is equal to the current time. Squids > further down the hierarchy do call storeNegativeCache() but they see > an expiration time that is already past so it isn't of any use. > > Those things make it seem like squid is far from being able to > effectively handle failing over from one origin server to another > at the application level. > > - Dave > > On Tue, Sep 30, 2008 at 10:32:43AM -0500, Dave Dykstra wrote: >> Do any of the squid experts have any answers for this? >> >> - Dave >> >> On Thu, Sep 25, 2008 at 02:04:09PM -0500, Dave Dykstra wrote: >> > I am running squid on over a thousand computers that are filtering data >> > coming out of one of the particle collision detectors on the Large >> > Hadron Collider. A bit off-topic here, but I'm wondering if these squids are being used in CERN's new computing grid? I noticed Fermi was helping out with this. (http://devicedaily.com/misc/cern-launches-the-biggest-computing-grid-in-the-world.html) Regards, Chris
