Tue Nov 29 13:29:10 PST 2011
- Previous message: [Slony1-bugs] [Bug 253] In the event of OID mismatch, slon confirms replication events without actually actioning them
- Next message: [Slony1-bugs] [Bug 178] More sophisticated FAILOVER
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=178 --- Comment #2 from Steve Singer <ssinger at ca.afilias.info> 2011-11-29 13:29:11 PST --- Since no patch was forthcoming for the original description I propose an alternative. I propose only to address the problem of a cluster like this Node 1-------------->Node 2 (set 1) (set 2) | | | | V V Node 3--------------> Node 4 If node 1 and 2 are both lost at the same time Assuming: - There are no oustanding configuration/subscription events at the time of failure. - No additional failures happen while the FAILOVER command is executing This patch proposes FAILOVER ( NODE=(ID=1,BACKUP NODE=2), NODE=(ID=3, BACKUP NODE=4)); It also includes a multi-node DROP NODE DROP NODE( id='1,2', event node=3); https://github.com/ssinger/slony1-engine/tree/multi_node_failover_steve Please review and comment on the syntax. -- 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.
- Previous message: [Slony1-bugs] [Bug 253] In the event of OID mismatch, slon confirms replication events without actually actioning them
- Next message: [Slony1-bugs] [Bug 178] More sophisticated FAILOVER
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list