On Thu, Mar 02, 2000 at 02:45:10PM -0600, Bob Duncan wrote:
> OK,
>
> Found it at http://www.bitmechanic.com/mail-archives/dbi-users/ , searched for
> DBD::Multiplex - found nothing...
>
> Any help?
The search on bitmechanic seems broken. Try the euro archive:
http://www.xray.mpe.mpg.de/mailing-lists/dbi/
Specifically:
http://www.xray.mpe.mpg.de/cgi-bin/w3glimpse/dbi?query=DBD%3A%3AMultiplex
Thomas Kishel <tkishel@stripped> is the developer [CC'd]
Tim.
>
>
> Thanks...
>
> -----Original Message-----
> From: Tim Bunce [SMTP:Tim.Bunce@stripped]
> Sent: Thursday, March 02, 2000 5:24 AM
> To: mocha mysql
> Cc: mark@stripped; Craig Vincent; mysql@stripped
> Subject: Re: True redundancy with MySQL
>
> See the dbi-users mailing list archives for DBD::Multiplex, which is
> designed to do this kind of thing.
>
> Tim.
>
> On Wed, Mar 01, 2000 at 07:53:35PM -0800, mocha mysql wrote:
> > this is a good idea.
> >
> > but here is another idea that has been bouncing in my
> > head for some time. how about a client/server process
> > running on each mysql server to do
> > mirroring/replication.
> >
> > for each mysql client program, you can have a list of
> > mysql server to query. on each mysql server you would
> > have a replication client and server daemon running.
> > this is NOT the same as the mysqld daemon but a
> > separate daemon.
> >
> > a query would go to the replicating daemon, that
> > daemon look through the list of available mysql
> > servers (mysqld) and hands off the query to one or all
> > of them. each replicating client on each server would
> > talk to the replicating daemon to make sure they are
> > all in sync.
> >
> > i hope that made sense. i think this could be
> > prototyped in perl rather quickly. this could also be
> > used to load balance each mysql server and query the
> > server with the lightest load.
> >
> >
> > --- Mark Ferraretto <mferrare@stripped> wrote:
> > > Another option is kind of a combination of both.
> > >
> > > I have to keep a copy of some of my database on my
> > > laptop for when I
> > > travel. The tables that I take have a 'sync' flag
> > > for each record. Every
> > > time I create or modify a record, it gets created
> > > and the 'sync' flag is
> > > set to 'N'. When I delete a record, the deleted
> > > flag is set to 'y' and
> > > sync is set to 'N'. Then, when I return to my
> > > office, I run a perl script
> > > that checks the server and my laptop for out of sync
> > > records and acts on
> > > them accordingly.
> > >
> > > You could implement something like this and have a
> > > perl script kick off
> > > every x minutes from cron to do the updating. This
> > > way both databases
> > > stay up and you don't get the problems associated
> > > with overwriting using
> > > FTP. Also, your CGI script only needs to do one
> > > update and your cron'd
> > > perl script handles the syncing. You write it so
> > > that the sync flag is
> > > the last thing changed and use date stamps to
> > > control race conditions,
> > > abmnormal terminations etc.
> > >
> > > If you want, I can send you my table structures and
> > > perl script. Let me
> > > know.
> > >
> > > Mark
> > >
> > > On Wed, 1 Mar 2000, Craig Vincent wrote:
> > >
> > > > Date: Wed, 1 Mar 2000 10:54:11 -0500
> > > > From: Craig Vincent <webmaster@stripped>
> > > > To: mysql@stripped
> > > > Subject: True redundancy with MySQL
> > > >
> > > > I know this question gets asked often, however the
> > > archives on the MySQL site seem outdated and I
> > > couldn't find any solutions there.
> > > >
> > > > I'm trying to come up with a solution for true
> > > redundancy on MySQL and so far have not come up with
> > > anything that isn't a disaster waiting to happen.
> > > Here were some potential theories:
> > > >
> > > > Assume there are two databases (A and B) and
> > > updates/inserts are done via a CGI script.
> > > >
> > > > Theory 1:
> > > >
> > > > Database A receives all updates from CGI. Every 5
> > > minutes or so FTP Database A and overwrite Database
> > > B. If Database A goes down CGI then sends all
> > > information to Database B
> > > >
> > > > Potential problems with this: Information updated
> > > since last A->B transfer will be lost. Perhaps
> > > doing some log parsing can retain the
> > > information...but this would require more than
> > > likely manual activation of a data retrieval script.
> > > B would also need to be copied back to A before CGI
> > > script realizes that DB A is back online...in a
> > > nutshell it requires precise timing, has potential
> > > race conditional and overall not fully automated
> > > >
> > > > Theory 2:
> > > >
> > > > CGI updates both Database A & B. During retrieval
> > > programs can access either server for the
> > > information.
> > > >
> > > > Potential problems:
> > > >
> > > > First off this will slow down the CGI and increase
> > > server load as it requires two connections & queries
> > > not just one. Also if one database goes down
> > > something needs to be done to get the database that
> > > went down up to speed. Can do parsing via log files
> > > but if times on servers are not exact there could be
> > > duplicated or lost data.
> > > >
> > > > So right now neither solution is appealing to me
> > > :( If someone has a working solution or can provide
> > > feedback on how I could improve either of the above
> > > theories please tell me. I'm open to all ideas and
> > > suggestions. Also rumour has it Linux was in the
> > > process of developing some sort of MySQL redundancy
> > > software...does anyone know if there's any truth to
> > > this?
> > > >
> > > >
> > > > Sincerely,
> > > >
> > > > Craig Vincent
> > > >
> > > >
> > >
> > > --
> > > Mark Ferraretto Phone: +61 8 8396
> > > 2448
> > > Ferraretto IT Services Fax: +61 8 8396
> > > 7176
> > > 26 Observation Drive Mobile: +61 407 95
> > > 97 19
> > > Highbury SA 5089 Email:
> > > mark@stripped
> > >
> > >
> > > --
> > >
> > ---------------------------------------------------------------------
> > > Please check
> > >
> > "http://www.mysql.com/Manual_chapter/manual_toc.html"
> > > before
> > > posting. To request this thread, e-mail
> > > mysql-thread29709@stripped
> > >
> > > To unsubscribe, send a message to:
> > >
> > >
> > <mysql-unsubscribe-mocha_mysql=yahoo.com@stripped>
> > >
> > >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> > --
> > ---------------------------------------------------------------------
> > Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
> > posting. To request this thread, e-mail mysql-thread29750@stripped
> >
> > To unsubscribe, send a message to:
> > <mysql-unsubscribe-Tim.Bunce=pobox.com@stripped>
> >
