On 5/26/2010 5:26 PM, bugzilla-daemon at main.slony.info wrote:
> http://www.slony.info/bugzilla/show_bug.cgi?id=130
> 
>            Summary: failover does not seem to update sl_set
>            Product: Slony-I
>            Version: 2.0
>           Platform: PC
>         OS/Version: Linux
>             Status: NEW
>           Severity: enhancement
>           Priority: low
>          Component: stored procedures
>         AssignedTo: slony1-bugs at lists.slony.info
>         ReportedBy: ssinger at ca.afilias.info
>                 CC: slony1-bugs at lists.slony.info
>    Estimated Hours: 0.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.
> 

Failover assumes that the failed node, in this case 1, is no longer 
reachable. There is no point in informing it about anything, so looking 
at status information of sets, tables or anything on node 1 does not 
make much sense.

The drop node should have an event node other than 1 specified and the 
code should check that event node and to be dropped node are different.


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin