You can run with "ignore-errors" at the top of each slave config file to get around this for now if you want to test further. It looks like the problem is in QueueProducer::queryForTrxIdList() it should not grab its own changes.
On Sat, Feb 25, 2012 at 3:43 PM, Daniel Nichter <[email protected]> wrote: > Master1: > > [master1] > master-host=127.0.0.1 > master-port=3002 > master-user=master > > Master2: > > [master1] > master-host=127.0.0.1 > master-port=3001 > master-user=slave > > Master1 is on port 3001, and master2 on port 3002. No auth or anything > else. I had wiped the tx logs before and started fresh. All the same, the > master1 error log shows it trying to apply an event it replicated to and > then read from master2. > > Le 25 févr. 2012 à 12:43, Joe Daly a écrit : > > Could you post your slave config files for each server? > > On Sat, Feb 25, 2012 at 2:02 PM, Daniel Nichter <[email protected]>wrote: > >> Dave, >> >> It seems master-master does not work in Drizzle. If I create a db on >> master1, it replicates to master2, and master2 writes the event to its repl >> log, which master1 then tries to reapply, causing the error on master1: >> >> (SQLSTATE 00000) Can't create schema 'test'; schema exists >> Failure while executing: >> COMMIT >> CREATE SCHEMA `test` COLLATE utf8_general_ci >> UPDATE `sys_replication`.`applier_state` SET `last_applied_commit_id` = >> 16, `originating_server_uuid` = '30433CCA-4655-4C37-9567-61749AA8A9FD' , >> `originating_commit_id` = 69 WHERE `master_id` = 1 >> >> UUID 304... is master1. I'm not familiar with the slave plugin code, but >> perhaps the SELECT statement in QueueConsumer::getMessage needs "WHERE >> originating_server_uuid != <my uuid>"? >> >> -Daniel >> >> Le 5 févr. 2012 à 13:12, David Shrewsbury a écrit : >> >> Hi Daniel, >> >> On Feb 5, 2012, at 1:19 PM, Daniel Nichter wrote: >> >> Just FYI to everyone: I'm in the process of updating the replication >> documentation which is currently wrong due to >> https://code.launchpad.net/~fallenpegasus/drizzle/multimaster/+merge/67103<https://code.launchpad.net/%7Efallenpegasus/drizzle/multimaster/+merge/67103>. >> This means that the examples in the docu don't work, nor do the example >> given by >> http://dshrewsbury.blogspot.com/2011/03/simple-drizzle-replication-example.htmland >> http://www.learningdrizzle.com/?p=97 because the slave plugin is >> multi-master which requires [masterN] headers in slave.cfg. I was puzzled >> why slave wasn't working this morning, stopping Drizzle from starting with >> this cryptic error message: "what(): unknown option master-host", >> extremely cryptic because "master-host" is correct. I had to look at the >> config filed used by slave tests to see that "[master1]" is now required. >> >> Also, talking with Monty this morning I realized more clearly the >> relationship between http://docs.drizzle.org/plugins/slave/index.htmland >> http://docs.drizzle.org/replication/drizzle.html which, as two separate >> entities, is probably confusing to users (it's been confusing to me). >> Therefore, I'm going to rewrite docs/replication/*. >> >> >> Thanks for taking on this task. My development skills far outweigh >> my documentation/communication skills, so your work here is much >> appreciated. And my time available to work on such stuff has seemed >> to disappear into the ether... >> >> Feel free to direct any questions you may have directly to me and >> I'll try my best to answer them. >> >> -Dave >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~drizzle-discuss >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~drizzle-discuss >> More help : https://help.launchpad.net/ListHelp >> >> > >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
