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

--- Comment #1 from Christopher Browne <cbbrowne at ca.afilias.info> 2010-06-15 15:25:07 PDT ---
(In reply to comment #0)
> Observed with 2.0.3
> 
> In a cluster as follows
> 
> 1
> \\
>  \\
>   3===4
>   \\
>    \\
>      5
> 
> 
>  A failover of set 1=>3 seems to work.
> 
> However DROP NODE (id=1) fails with 
> 
> <stdin>:12: PGRES_FATAL_ERROR select "_disorder_replica".dropNode(1);  - ERROR:
>  Slony-I: Node 1 is still origin of one or more sets
> 
> When I query sl_set it shows that node 1 is still the origin of the set even
> though the failover command seemed to work okay.

Where did you run these commands?

If you did so against node 1, then I'd fully expect this behaviour.  Node #1
doesn't really know that it's "shunned."  It certainly doesn't if the disks
were ground into a powder (in which case your queries would fail because
there's no database there anymore!).

But if node 1 failed due to a network partition, it can't expect to ever be
aware that it's shunned.

If the requests were hitting ex-node #1, then I don't think these results are
necessarily 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.