> From: "Ralph Graulich"
> > Read about "replication" in the corresponding chapters in the online
> manual
> > of mySQL (http://www.mysql.com/) -> Documentation.
>
> From: "Mat Murdock"
> > Did you look at doing something with replication?
>
> Thanks for the quick reply. I hadn't looked at replication previously. I've
> read the text about it now, and might have missed something. But..
>
> In the setup I'm looking for there is no clear master-slave relationsship.
> With this in mind I could setup numerous servers to all act master to all
> others. This would be way of keeping all in sync. There are problems with
> this setup (as stated in the manual), ie. things are not allowed to go wrong
> if updates are done in slightly different choronological order. I understand
> why this is so. This would be a problem for all but very simplistic
> informations.
>
>
> In our setup the different db's aren't backups (slaves), but all are used as
> masters (they're located differently geographicaly). I guess I'm looking for
> a 'clustered' service where all db's act as if there we a single one. I
> didn't expect MySQL to handle this out of the box but was hoping there was a
> 3rd party add-on/sub system/super system through which it could be 'easely'
> done.
>
For what it's worth, we currently have multiple 'master' databases
running in different geographic locations (London England, Monetery
California, Waterloo Ontario) What we have had to do is set up the
replication in a circle:
ie Montrey -> Waterloo -> London
^-----------------
seems to work fine so far, although we haven't really stressed the
system yet, only ~1 update/sec, but it appears that the transmission
speed would be the only bottleneck. Updates tend to get into all of the
databases incredibly fast (~1sec for updates on all systems for the most
part)
Another thing that I'm not positive about is whether or not the servers
talk over a compressed channel to each other...
One thing that we did have to do is increase the timeouts for the
net_read_timeout and net_write_timeout because we were running into
dropped connections due to long transmissions...
We are also currently primarily updating a single server, but we have
tested updating any of the machines, and the updates get to all of them.
I have not heard of any way to have multiple masters for a specific
mysql server, although I have heard of running multiple instances of
mysql on a single machine to be able to replicate multiple machines onto
a single machine...
Hope that this helps.
Scott V
---------------------------------------------------------------------
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
