[Spread-users] mod_log_spread errors in error_log

[Monte Ohrt]

George Schlossnagle wrote:
> 
> > Ok great! This is my first time putting spread and mod_log_spread to the
> > test with production systems, so a couple more questions I have:
> >
> > * How do you suggest the spread daemon be started on the apache hosts?
> > Right now I'm starting with an init.d start/stop script. The problem is
> > if the spread daemon dies, the logs will be lost for this host, yes?
> > Should I run spread from inittab, or should I monitor the daemon
> > process? What are others doing?
> 
> That's an interesting idea.  I run mine from cron every minute and just let
> it fail to bind if it's already running.

That sounds like a lot of unnecessary process inits and error logs to me
;-)

> 
> >
> > * heavy traffic configuration
> > All my spread hosts are on one network segment (100mb), currently I have
> > about 100 virtual hosts, we're probably seeing 3-5 million hits a day
> > collectively. I only have a few servers now, but this will grow over
> > time, as will the hits. Is this a walk in the park for spread, or is
> > this considered  to be heavy traffic?
> 
> That should be fine.
> 
> >   * What is the most efficient way to run spread?  Should I put all the
> > machines into one segment in the config file? I am limited to 128
> > systems per segment, correct?
> 
> I would recommend a single ring up to around 10-15 hosts, or as  long as it
> stays stable.

... and how will I know when this is unstable? apache error_log, or
somwhere else?

> 
> >   * Are the default WATER_MARK and MAX_SESSION_MESSAGES values adequate?
> >

Monte