On Sat, Oct 04, 2008 at 12:55:15PM -0400, Chris Nighswonger wrote:
On Tue, Sep 30, 2008 at 6:13 PM, Dave Dykstra [EMAIL PROTECTED] wrote:
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
Mark,
Thanks for that suggestion. I had independently come to the same idea,
after posting my message, but haven't yet had a chance to try it out. I
currently have hierarchies of cache_peer parents but stop the hierarchies
just before the last step to the origin servers because they were
Henrik,
Thanks so much for your very informative reply!
On Thu, Oct 02, 2008 at 12:31:03PM +0200, Henrik Nordstrom wrote:
By default Squid tries to use a parent 10 times before declaring it
dead.
Ah, I never would have guessed that I needed to try 10 times before
negative_ttl would take
On tis, 2008-10-07 at 11:49 -0500, Dave Dykstra wrote:
Ah, I never would have guessed that I needed to try 10 times before
negative_ttl would take effect for a dead host. That wouldn't be
bad at all.
You don't. Squid does that for you automatically.
time I still saw the request get sent
On Tue, Oct 07, 2008 at 08:38:12PM +0200, Henrik Nordstrom wrote:
On tis, 2008-10-07 at 11:49 -0500, Dave Dykstra wrote:
Ah, I never would have guessed that I needed to try 10 times before
negative_ttl would take effect for a dead host. That wouldn't be
bad at all.
You don't. Squid
Hi Dave,
On Tue, Sep 30, 2008 at 6:13 PM, Dave Dykstra [EMAIL PROTECTED] 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
By default Squid tries to use a parent 10 times before declaring it
dead.
Each time Squid retries a request it falls back on the next possible
path for forwarding the request. What that is depends on your
configuration. In normal forwarding without never_direct there usually
never is more than at
Have you considered setting squid up to know about both origins, so it
can fail over automatically?
On 26/09/2008, at 5:04 AM, 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
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. There are
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:
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. There are two origin servers, and the application
layer is designed to try the second server if the local squid returns a
5xx HTTP code
11 matches
Mail list logo
