On 12/5/2005 3:07 PM, Christopher Browne wrote:

> Melvin Davidson wrote:
> 
>> Question on an anomaly.
>>
>> I am currently testing slony slony1-1.1.2 on 3 nodes configured as
>> follows:
>>
>> node 1                    node 2                  node 3
>> MASTER ------>  SLAVE1 -------> SLAVE2
>>
>> All works correctly.
>> However, I noticed that after doing a switchover to SLAVE1:
>> ==================================
>> lock set (id = 1, origin = 1);
>> wait for event (origin = 1, confirmed = 2);
>> move set (id = 1, old origin = 1, new origin = 2);
>> wait for event (origin = 1, confirmed = 2);
>> ==================================
>>
>> slon on SLAVE2 stops.
>> It can be restarted successfully, but I am wondering if this is
>> expected behavior, as it is not documented that this will occur.
>>
>> Why would the other slave(s) stop during a switchover?
> 
> It *is* necessary, upon this action, that configuration be reloaded, so
> that the various nodes are aware of the change of node roles.
> 
> In version 1.2, this probably won't involve the slon actually falling over.

I is fixed in HEAD. It will not be backported into 1.1.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #