----- Original Message -----
> From: Steve Singer <ssinger at ca.afilias.info>
> To: Glyn Astill <glynastill at yahoo.co.uk>; "slony1-general at lists.slony.info" <slony1-general at lists.slony.info>
> Cc: 
> Sent: Tuesday, 6 May 2014, 20:29
> Subject: Re: [Slony1-general] Slony 2.2 failover changes
> 
> On 05/06/2014 11:49 AM, Steve Singer wrote:
>>  On 05/06/2014 10:54 AM, Steve Singer wrote:
>>> 
>>> 
>>>  I see what is going on (based on the logs you sent that the list 
> didn't
>>>  like)
>>> 
>>> 
>>>  node 4 is configured to use node 2 as the provider for the set
>>> 
>>>  Node 4 has the following in its event queue
>>> 
>>>  1,5000000111 SYNC
>>>  .
>>>  .
>>>  1,5000000118 FAILOVER_NODE
>>> 
>>>  remoteWorker_1 on node 4 doesn't process the FAILOVER_NODE because 
> it
>>>  can't get beyond the SYNC.  It can't get beyond the SYNC 
> because the
>>>  provider for 1 is 2 which has gone offline.
>>> 
>> 
>>  I *suspect* the attached patch might fix the issue, but I haven't yet
>>  done much testing with it.
>> 
> 
> Testing shows that more is needed than just that  change.
> I'll open a bug once I have a more refined patch.
> 
> 

Thanks Steve, I'll wait for that then re-run my test.