Re: Problem with origin server connections

Brian put together a hack to the dns guts which sends them to a
different origin server each time and does some health checking on them
to see if any more requests should be sent to each origin server. It
would be nice to use the new rproxy setup to do this, but it is not in
the stable releases yet.

On Mon, 2003-03-10 at 16:45, Henrik Nordstrom wrote:
> How are you making Squid distribute the requests on the backend
> servers?
>
> Regards
> Henrik
>
> On Monday 10 March 2003 22.13, David Nicklay wrote:
> > Hi,
> >
> > Brian and I have been trying to puzzle out a problem we are having
> > related to back end origin server connections initiated by squid.
> > We have squid (2.5.stable1) set up in a reverse proxy configuration
> > pointing at a group of origin servers which mount a number of NFS
> > mounts to serve content from. What we are seeing is that when one
> > of those NFS mount points locks up on the origin server, it will
> > cause a seemingly permanent change to the number of connections and
> > back end refreshes that the squid servers are sending to the
> > origins. Restarting the squid listeners fixes it, but if we do not
> > restart them, the number of connections and refreshes never returns
> > to its normal state. This is true even if the NFS mount point
> > comes back and the origin servers are restarted.
> >
> > I have seen this go on for over a day, when all of our timeouts are
> > set in minutes and seconds not hours or days. I am curious to know
> > why this behavior exists, and if there is anything that could be
> > done about it? I am asking here rather than the squid user list,
> > because I think it may be something fundamental to the way squid
> > works and not a configuration issue.

-- 
David Nicklay
Location: CNN Center - SE0811A
Office: 404-827-2698	Cell: 404-545-6218