List:General Discussion« Previous MessageNext Message »
From:Rick James Date:July 24 2013 5:52pm
Subject:RE: Replication question
View as plain text  
> 4) 3 tables from the slaves are to be replicated back to the master

However, consider Percona XtraDb Cluster or MariaDB+Galera.  They allow multiple writable
masters.  But they won't let you be so selective about tables not being replicated.
Here are the gotchas for Galera usage:
If you can live with them (plus replicating everything), it may be best for you.

> -----Original Message-----
> From: rich gray [mailto:rich@stripped]
> Sent: Wednesday, July 24, 2013 8:21 AM
> To: mysql@stripped
> Subject: Replication question
> I have been asked to set up multiple database replication which I have
> done before for simple cases however there are some nuances with this
> instance that add some complexity and I'd like to hear your collective
> expertise on this proposed scenario:-
> 1) Single master database
> 2) n (probably 3 to start with) number of slave databases
> 3) All but 5 tables (123 tables in total) are to be replicated from the
> master to all the slaves
> 4) 3 tables from the slaves are to be replicated back to the master
> It is mainly item 4) that concerns me - the primary ID's are almost
> certain to collide unless I seed the auto increment ID to partition the
> IDs into separate ranges or does MySQL handle this issue?
> There are some foreign keys on one of the 3 slave to master tables but
> they are pointing at some extremely static tables that are very unlikely
> to change.
> Is the above a feasible implementation...?
> Thanks in advance for any advice/pointers!
> Rich
> --
> MySQL General Mailing List
> For list archives:
> To unsubscribe:

Replication questionrich gray24 Jul
  • RE: Replication questionRick James24 Jul
    • Re: Replication questionrich gray25 Jul