> > > In case anybody else comes across the same, I've kicked out the MySQL > cluster and now using MySQL with multi-master replication. There we can > use InnoDB and this definitely solved all of the problems I had with > bayes. Scantimes are now below 1 second. I don't have much load as of > yet, so I expect this to increase somewhat during business hours, but > all in all things look a lot more promising. I've used this howto: > http://capttofu.livejournal.com/1752.html >
Hi Jorn I'm running the same kind of multimaster mysql replication scheme (my sql ndoes are in different datacenters so a cluster was not a good option for us) However I've seen several reports of people having problem with bayes and replication, since with multimaster replication you have to manually be sure there is no overlap in row id's etc. I cant remember 100% if it was an old issue or if it still should be an issue, I just thought I'd send you this warning, that replication might break if you habve a bayes DB on the dbms and the 2 masters write the same id/token whatever to the DB. So you might want to test thoroughly before you deploy in production, or at least if it breaks later you might remember this mail :) Med venlig hilsen / Best regards Jonas Akrouh Larsen TechBiz ApS Laplandsgade 4, 2. sal 2300 København S Office: 7020 0979 Direct: 3336 9974 Mobile: 5120 1096 Fax: 7020 0978 Web: www.techbiz.dk
