Tue May 25 14:29:10 PDT 2010
- Previous message: [Slony1-bugs] [Bug 128] New: DROP TABLE replicatedTable leaves the cluster in a bad state
- Next message: [Slony1-bugs] [Bug 130] New: failover does not seem to update sl_set
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=129 Summary: FAILOVER command does not update sl_subscriber Product: Slony-I Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: low Component: slonik 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 is with 2.0.3 On a cluster where nodes 4 and 5 are cascded from 3. 1===>3=====>4 \\ 5 The slonik script -- FAILOVER(id=3,backup node=1); echo 'the failover command has completed'; --- Slonik exists normally and seems to execute the script with no errors (it prints - <stdin>:13: the failover command has completed ) but then select * FROM _disorder_replica.sl_subscribe ; sub_set | sub_provider | sub_receiver | sub_forward | sub_active ---------+--------------+--------------+-------------+------------ 1 | 1 | 2 | t | t 1 | 1 | 3 | t | t 1 | 3 | 4 | t | t 1 | 3 | 5 | t | t shows node 3 still as the provider for nodes 4 and 5. -- 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 128] New: DROP TABLE replicatedTable leaves the cluster in a bad state
- Next message: [Slony1-bugs] [Bug 130] New: failover does not seem to update sl_set
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list