Thu Oct 17 13:36:34 PDT 2013
- Previous message: [Slony1-bugs] [Bug 292] sl_log_1 & sl_log_2 table not cleaning
- Next message: [Slony1-bugs] [Bug 322] clone prepare can fail to replicate
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=322 Summary: clone prepare can fail to replicate Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: stored procedures AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 This issue has been periodically observed with the disorder CLONE NODE test. slon3 can encounter the following in its slon log ----------- remoteWorkerThread_5: SYNC 5000000002 done in 0.000 seconds remoteWorkerThread_2: SYNC 5000000002 done in 0.001 seconds storeNode: no_id=6 no_comment='Node 6' remoteWorkerThread_2 error querying last confirmed id for node 6 in CLONE NODE - ERROR: duplicate key value violates unique constraint "sl_node-pkey" What appears to be happening is that slon 3 sees the STORE NODE between node 6 and some other node BEFORE it sees the CLONE NODE that creates node 6. sl_node has a entry for no_id=6 with <event pending> and the cloneNodePrepare_int() fails because of that. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 292] sl_log_1 & sl_log_2 table not cleaning
- Next message: [Slony1-bugs] [Bug 322] clone prepare can fail to replicate
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list