Wed Oct 22 15:33:53 PDT 2014
- Previous message: [Slony1-bugs] [Bug 354] New: failover can get stuck waiting for events after sl_listen is empty
- Next message: [Slony1-bugs] [Bug 354] failover can get stuck waiting for events after sl_listen is empty
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=354 --- Comment #1 from Steve Singer <ssinger at ca.afilias.info> 2014-10-22 15:33:53 PDT --- In RebuildListenNetwork we have the following comment --for every failed node we delete all sl_listen entries --except via providers (listed in sl_subscribe) --or failover candidates (sl_failover_targets) --we do this to prevent a non-failover candidate --that is more ahead of the failover candidate from --sending events to the failover candidate that --are 'too far ahead' delete from @NAMESPACE at .sl_listen where li_origin=v_row.origin and li_receiver=v_row.receiver and li_provider not in (select sub_provider from @NAMESPACE at .sl_subscribe, @NAMESPACE at .sl_set where sub_set=set_id and set_origin=v_row.origin); node 5 isn't a provider of anything so the listen network is erased. I think this is wrong. -- 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 354] New: failover can get stuck waiting for events after sl_listen is empty
- Next message: [Slony1-bugs] [Bug 354] failover can get stuck waiting for events after sl_listen is empty
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list