On Mon, Jan 25, 2010 at 10:19 PM, Richard Yen <dba at richyen.com> wrote:
>
> On Jan 25, 2010, at 9:12 PM, Richard Yen wrote:
>
>>
>> On Jan 14, 2010, at 9:06 AM, Christopher Browne wrote:
>>>> Does the below line mean it is waiting for some kind of notification
>>>> from somewhere? :
>>>> DEBUG2 ACCEPT_SET - MOVE_SET or FAILOVER_SET not received yet -
>>>> sleep
>>> Yup, that indicates that node #3 hasn't completed the failover.  It
>>> hasn't fully accepted the new provider.
>>> I'm not sure what to suggest on that.
>>
>> I'm actually experimenting with this issue on slony 2.0.3 rc3.  It
>> seems that there is a race condition (I'm still trying to pinpoint
>> exactly where it is) where if you call the DROP_NODE command before
>> the FAILOVER_SET command is completed, the ACCEPT_SET command never
>> makes it into sl_event.
>
> Sorry, I should be a little more specific.  It looks like when the
> FAILOVER_SET command finishes in slonik, the events have not
> necessarily been propagated to the slaves (they're only issued to the
> new master so far).  Therefore, when the DROP_NODE command is called,
> there is no ACCEPT_SET entry in sl_event on the slaves, thus causing
> the DROP_NODE to flounder, and it will keep retrying and failing.
>
> Hopefully that makes it a little more clear when I said "the
> ACCEPT_SET command never makes it to sl_event"

Does running a SYNC between them allow it to work?