Thu Jun 3 18:32:16 PDT 2010
- Previous message: [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber
- Next message: [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=129 --- Comment #2 from Steve Singer <ssinger at ca.afilias.info> 2010-06-03 18:32:16 PDT --- The approach that I described in my last note won't work. The slonik script doesn't know which node slonik posted the event into, thta node is determined by slonik at runtime. Issuing a sync against the new origin and waiting for it to be confirmed doesn't seem to ensure that the accept set posted against some other node gets confirmed on all nodes. Also doing a wait for event(confirmed=all) can be problametic here since the failed node has not yet been dropped (we can't drop it until the failover properly completes) but if that node really failed it won't be able to confirm any events. -- 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 129] FAILOVER command does not update sl_subscriber
- Next message: [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list