Hi,
I wonder (i don't tested) if is possible to start two session of mysqld on
each machine which work on the same database : one for master and one for
slave.
MACHINE1 MACHINE2
1.Master Session ---------> 1.Slave Session
2.Slave Session <--------- 2.Master Session
| |
DataBase DataBase
...else ,in my opinion, i consider is necessary to develop a server
application to solve full duplex replication.
Regards,
Gelu
_____________________________________________________
G.NET SOFTWARE COMPANY
Permanent e-mail address : [EMAIL PROTECTED]
[EMAIL PROTECTED]
----- Original Message -----
From: "Jeremy Zawodny" <[EMAIL PROTECTED]>
To: "Christophe Demange" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, May 11, 2002 1:07 AM
Subject: Re: Distributed MySQL : How to synchronize ?
> On Fri, May 10, 2002 at 04:51:15PM +0200, Christophe Demange wrote:
> > Hello,
> >
> > I have a question:
> >
> > We want to real-time synchronize a MySQL database part with a
> > distant database. We have a central database containing all the
> > data. This database must share several parts (records) with the
> > local databases. All transactions made in the central database must
> > be replicated to the corresponding local database. This will ensure
> > to have the data available while the network is down. In the same
> > time some transactions can be made in the local database, this
> > includes to have a dual-way replication mechanism.
>
> Hmmm.
>
> > I have searched replication documentation and articles and I have
> > only found master-slave relationship. We think this master-slaves
> > relationship doesn't exactly fit our needs.
>
> It probably doesn't, but...
>
> > Please could you explain us what is the best solution to use for
> > this architecture.
>
> Since you asked, here's a thought that'll require a bit of research
> and testing on your end. It might get you some of the way there.
>
> Rather than write records to a single table on the master, break
> things out into several identically structured tables. The create a
> MERGE table out of them. Run your write queries against the
> underlying table appropriate for the record.
>
> That *may* allow the slaves to replicate only the data they need. I
> say "may" because I don't know enough about your application to make
> that judgement.
>
> The only problem arises in the getting updates made on the slaves back
> to the master. A slave in MySQL can only have one master, so that's a
> more difficult problem.
>
> Jeremy
> --
> Jeremy D. Zawodny, <[EMAIL PROTECTED]>
> Technical Yahoo - Yahoo Finance
> Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936
>
> MySQL 3.23.47-max: up 92 days, processed 2,403,910,165 queries (301/sec.
avg)
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
