From: Michal L. <mi...@lo...> - 2007-08-21 14:38:18
|
Andrew Rose wrote: > I am currently running a chained master->master setup. It is a common > MySQL replication problem with master->master setups, and crops up > when the PK's are not auto incrementing. So it isn't MySQL error but an improper MySQL configuration ;-) In case of master-master you have to ensure that each server generates different keys, not that apps will somehow take care of it. Common solution is to make one master generate sequence 1,3,5,... and the second master 2,4,6,... In the case you run more than two masters you'll obviously increase the stepping to accommodate them all. Check out this page for details: http://dev.mysql.com/doc/refman/5.0/en/replication-auto-increment.html > I figured there would be a problem with threading. Have you thought > about maybe providing some shared memory locking functionality? ;) Not in the immediate future, sorry. I don't do any active development on mysqlfs anymore. > Many thanks for the help. For now I think I'll keep my fingers > crossed and hope that what I have done has lowered the odds enough > that I will rarely, if ever, see a problem, considering there is > minimal writes going on to my mounted filesystems anyway. I suggest you reconfigure the DB instead of crossing fingers ;-) Michal |