Fri Jan 25 13:57:21 PST 2013
- Previous message: [Slony1-bugs] [Bug 273] Slon can try to pull data from a behind provider.
- Next message: [Slony1-bugs] [Bug 285] move set issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=285 Summary: move set issues Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: enhancement Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 We appear to have a bug in move set where nodes can get out of sync 1. A user reported that they were doing a series of move sets and ended up having encountering a unique key violation when slon tried to replicate data from one node to another. The user didn't have logging set high enough to determine a definite cause. They were running Slony 2.1 2. In REL_2_1_STABLE and master running the disorder MoveSet test continuously once in a while produces failures. In at least some cases the cluster seems to get into a state where a subscriber node (that isn't the old or new origin) has no sl_setsync rows. The slon will then process/confirm SYNC's for nodes that it SHOULD be subscribed to but doesn't select anything from sl_log_1 The exact cause of these issues is still unknown but they seem to be occasionally reproducible -- 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 273] Slon can try to pull data from a behind provider.
- Next message: [Slony1-bugs] [Bug 285] move set issues
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list