http://www.slony.info/bugzilla/show_bug.cgi?id=80





--- Comment #1 from Christopher Browne <cbbrowne at ca.afilias.info>  2009-04-09 15:10:59 ---
I'll think about this over the weekend; my first reaction is to treat this as a
documentation patch, and to recommend not rushing to drop the node out of the
cluster until you actually get the failover completed.

As a first response, that's definitely what I'd recommend.

When you drop it "too quickly," that introduces the risk, which you ran into,
that some later node gets the DROP NODE event before receiving the FAILOVER
event.

There's no easy way to evade that problem!

However, second reaction is that it's not particularly reasonable for this
mistake to be allowed to break the cluster.

As a first thought on a solution, we might check to see if there's a pending
FAILOVER_SET event pending, and somehow defer/ignore the DROP NODE.

Gonna have to sleep on that...


-- 
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.