[Dbbalancer-users] Re: Request for comments

[Daniel V. S. <dv...@ar...>]

On Sun 04 Nov 2001 00:13, you wrote:

> The idea I have so far is:
>
> 1) Have a directory of configuration scripts for the various databases
> to be 'balanced'.  I would make this directory in /etc/dbbalancer/conf.d
> which would conform to the way Debian does these sorts of things.
>
> 2) My init script would then go through each configuration file in the
> directory, starting a DBBalancer daemon for each one.

I see a problem with this one. The "reader" or "writer" operation is not 
thought to be extracted from the configuration file, as this file should be 
shared between a reader and a writer. The difference was in the "-r" or "-w" 
parameter. Maybe it could be better to use different config files for the 
reader and the writer, but they share almost all parameters (except for the 
port)... We have to find the best solution for this...

>
> 3) The process ID for each process would be written in
> /var/run/dbbalancer/<confname>

I'll have to make this path configurable, just like the UNIX socket path has 
to be.

>
> 4) When run with a 'stop' parameter, the init script would kill each
> process.
>
> Anyone have any comments on that approach?

If we find a way for reader/writer thing, I agree

>
>
> Also, a few of things that would be good to see in the current
> DBBalancer to support this sort of operation:
>
> 1) Less logging.  Currently DBBalancer logs every connection - this
> seems a bit excessive for a website receiving a hundred thousand hits
> each day.  Although it might be fine to have this level of logging as a
> default, it would be nice to be able to reduce it further.

That's easy with ACE. I'll put that on 0.4.1.

>
> 2) 'Detach and run as daemon' option.  DBBalancer really is a service,
> and it should detach itself from the console and run in background.
> This should probably be the default operation, although while we
> consider things to be 'alpha' perhaps it should only be an option.

We can make it detach only when debug is disabled. Or maybe better set a new 
parameter. I've looked to "postmaster.c" code ...

>
> 3) Logging through syslog.  In normal operation I am likely to have a
> number of DBBalancer daemons operating at the same time, in background,
> it will be desirable to collect their error messages in one place.  I
> would tend towards specifying a log facility in the configuration file,
> and using syslog.

This is also easy with ACE. I only have to figure "how" ;-)

>
> With these enhancements, along with fixes to the little niggles that
> have come up in the last couple of days with 0.4, I believe we are
> probably ready to call it a 'beta', and I will put packages into the
> 'unstable' branch of Debian.
>
> Comments?

Well. I fully agree with the last three. The others are also good, but maybe 
I have to change the way "readers" and "writers" are differentiated. Not a 
big problem, anyway.

>
> Regards,
> 						Andrew.

-- 

----------------------------------
Regards from Spain.  Daniel Varela
----------------------------------

If you think education is expensive, try ignorance.
           -Derek Bok (Former Harvard President)