[EMAIL PROTECTED] wrote:
> 
> Pier Fumagalli wrote:

> > > I'm still seeing erratic ssh response.  Is there some way to monitor network
> > > bandwidth utilization in real time?  I wonder if we are maxing out our NICs
> > > this morning?  That would make the big downloads take longer, using up more httpd
> > > processes.  If that's our problem, maybe we should pursue Joshua Slive's idea
> > > of redirecting requests for the most popular downloads to a reliable mirror, like
> > > nagoya.
> 
> > Please, feel free to redirect
> >
> > www.apache.org/dist/httpd/(.*)   -> nagoya.apache.org/dist/httpd/$1
> > www.apache.org/dist/jakarta/(.*) -> nagoya.apache.org/dist/jakarta/$1
> > jakarta.apache.org/builds/(.*)   -> nagoya.apache.org/dist/jakarta/$1
> > www.apache.org/dist/xml/(.*)     -> nagoya.apache.org/dist/xml/$1
> > Xml.apache.org/dist/(.*)         -> nagoya.apache.org/dist/xml/$1
> >
> > This should take some load away from daedalus, and maybe give you a better
> > chance to investigate the problem further... Right now it's kinda of
> > unbearable on there...
> 
> Well, I don't feel brave enough to redirect all of that at once without knowing
> what's going on in the xml or jarkarta projects, and without being able to
> monitor nagoya very well.  But I did add:
> 
> Redirect /dist/httpd/binaries http://nagoya.apache.org/dist/httpd/binaries

We are maxed out on httpds this morning, and httpd response is poor.  There
isn't much load:

load averages:  0.94,  1.35,  2.34

Even though MaxClients is 800, we only have 776 child processes.  I think this
is because we're not cleaning up the scoreboard properly after I dropped
MaxClients via graceful restart. 

Here's a plan: non-graceful restart with MaxClients at 820, and at the same time
redirect the current httpd source tarballs and
/jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/ to nagoya.  That
should free up bandwidth on daedalus.  MaxClients 820 looked OK for quite a
while yesterday.  If it's too much, we can bring MaxClients down via graceful;
raising it with a dirty scoreboard is the piece that doesn't work.

I don't want to redirect the jakarta nightly builds though, or everything under
/www.apache.org/dist/httpd/ , because then people wouldn't be able to access
files between the time daedalus gets updated and the time nagoya mirrors the
update. 

Greg

Reply via email to