Thu Sep 25 09:28:05 PDT 2008
- Previous message: [Slony1-bugs] Cache lookup failure when starting slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=57 Summary: Missing data and syncs ignored Product: Slony-I Version: 1.2 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: medium Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: meetesh.karia at alumni.duke.edu CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 We've been running slony (currently on version 1.2.14) for a while and recently we ran into a situation where a SYNC was failing due to a constraint violation exception. After looking into why that happened, I was able to see that some deletes that occurred on the master were never propagated to the slave and that then caused the constraint violation further down the road. To add to the mysteriousness, after the SYNC had been tried numerous times, it finally just decided to do nothing for the SYNC and continue on. Our setup has a postgres 8.3.1 db running on the master with a slave (slave 1) on the same LAN. We also have a slave (slave 2) in another environment with that replication happening over a WAN (there is a separate slon daemon running in the other environment). Events were going from the master to slave 1 and then slave 1 was set up as a provider for slave 2. This may or may not be an issue, but we've occasionally seen network issues between our two environments. However, the issue occurred with slave 1 so it happened before it got to the network between the two environments. Here is a snippet of the log file showing how the SYNC was ignored: 2008-09-24 23:04:32 CDT DEBUG2 remoteWorkerThread_3: SYNC 262954 processing 2008-09-24 23:04:32 CDT DEBUG2 remoteWorkerThread_3: syncing set 3 with 3 table(s) from provider 3 2008-09-24 23:04:32 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:32 CDT DEBUG2 remoteWorkerThread_3: syncing set 5 with 1 table(s) from provider 3 2008-09-24 23:04:32 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:32 CDT DEBUG2 remoteWorkerThread_3: syncing set 2 with 1 table(s) from provider 3 2008-09-24 23:04:32 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:32 CDT DEBUG2 remoteWorkerThread_3: syncing set 1 with 51 table(s) from provider 3 2008-09-24 23:04:32 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:32 CDT DEBUG2 remoteWorkerThread_3: current local log_status is 0 2008-09-24 23:04:32 CDT DEBUG2 remoteWorkerThread_3_3: current remote log_status = 0 2008-09-24 23:04:32 CDT DEBUG2 remoteHelperThread_3_3: 0.056 seconds delay for first row 2008-09-24 23:04:32 CDT DEBUG2 remoteHelperThread_3_3: 0.063 seconds until close cursor 2008-09-24 23:04:32 CDT DEBUG2 remoteHelperThread_3_3: inserts=49 updates=0 deletes=0 2008-09-24 23:04:32 CDT ERROR remoteWorkerThread_3: <snip> " ERROR: duplicate key value violates unique constraint "idx_unique_calendar_entry" - qualification was: 2008-09-24 23:04:32 CDT ERROR remoteWorkerThread_3: SYNC aborted 2008-09-24 23:04:33 CDT DEBUG2 remoteListenThread_3: queue event 3,263077 SYNC 2008-09-24 23:04:33 CDT DEBUG2 remoteListenThread_3: UNLISTEN 2008-09-24 23:04:35 CDT DEBUG2 remoteListenThread_4: queue event 4,107043 SYNC 2008-09-24 23:04:35 CDT DEBUG2 remoteWorkerThread_4: Received event 4,107043 SYNC 2008-09-24 23:04:35 CDT DEBUG2 calc sync size - last time: 1 last length: 10053 ideal: 5 proposed size: 3 2008-09-24 23:04:35 CDT DEBUG2 remoteWorkerThread_4: SYNC 107043 processing 2008-09-24 23:04:35 CDT DEBUG2 remoteWorkerThread_4: no sets need syncing for this event 2008-09-24 23:04:38 CDT DEBUG2 syncThread: new sl_action_seq 1 - SYNC 107646 2008-09-24 23:04:39 CDT DEBUG2 localListenThread: Received event 1,107646 SYNC 2008-09-24 23:04:40 CDT DEBUG2 remoteWorkerThread_4: forward confirm 4,107043 received by 3 2008-09-24 23:04:41 CDT DEBUG2 remoteListenThread_3: LISTEN 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3: SYNC 262954 processing 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3: syncing set 3 with 3 table(s) from provider 3 2008-09-24 23:04:42 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3: syncing set 5 with 1 table(s) from provider 3 2008-09-24 23:04:42 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3: syncing set 2 with 1 table(s) from provider 3 2008-09-24 23:04:42 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3: syncing set 1 with 51 table(s) from provider 3 2008-09-24 23:04:42 CDT DEBUG2 ssy_action_list length: 0 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3: current local log_status is 0 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3_3: current remote log_status = 0 2008-09-24 23:04:42 CDT DEBUG2 remoteHelperThread_3_3: 0.018 seconds delay for first row 2008-09-24 23:04:42 CDT DEBUG2 remoteHelperThread_3_3: 0.034 seconds until close cursor 2008-09-24 23:04:42 CDT DEBUG2 remoteHelperThread_3_3: inserts=0 updates=0 deletes=0 2008-09-24 23:04:42 CDT DEBUG2 remoteWorkerThread_3: SYNC 262954 done in 0.055 seconds -- 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] Cache lookup failure when starting slony
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list