-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Glyn,

Glyn Astill a écrit :
> I'm still trying to figure this one out chaps.
> 
>>From what I can see the move set command moved the origin from 1 to 2 successfully, but why is node 3 still subscribed to node 1? Surely it should have had it's subscribtion moved to node 2?
> 
> Here's sl_subscribe
> 
> SEE=# select * from _main_replication.sl_subscribe order by sub_provider, sub_set;
>  sub_set | sub_provider | sub_receiver | sub_forward | sub_active
> ---------+--------------+--------------+-------------+------------
>        1 |            1 |            3 | t           | t
>        2 |            1 |            3 | t           | t
>        3 |            1 |            3 | t           | t
>        4 |            1 |            3 | t           | t
>        5 |            1 |            3 | t           | t
>        6 |            1 |            3 | t           | t
>        7 |            1 |            3 | t           | t
>     1000 |            1 |            3 | t           | t
>        1 |            2 |            1 | t           | t
>        2 |            2 |            1 | t           | t
>        3 |            2 |            1 | t           | t
>        4 |            2 |            1 | t           | t
>        5 |            2 |            1 | t           | t
>        6 |            2 |            1 | t           | t
>        7 |            2 |            1 | t           | t
>     1000 |            2 |            1 | t           | t
> (16 rows)
> 
> And here's what I did;
> 
> CLUSTER NAME = main_replication;
> NODE 1 ADMIN CONNINFO = 'dbname=SEE host=192.168.240.10 user=slony';
> NODE 2 ADMIN CONNINFO = 'dbname=SEE host=192.168.240.11 user=slony';
> NODE 3 ADMIN CONNINFO = 'dbname=SEE host=192.168.240.12 user=slony';
> 
> DEFINE set_to_move 1;
> DEFINE old_origin 1;
> DEFINE new_origin 2;
> DEFINE other_node 3;
> 
> LOCK SET ( ID = @set_to_move, ORIGIN = @old_origin);
> 
> WAIT FOR EVENT (ORIGIN = @old_origin, CONFIRMED = @new_origin);
> WAIT FOR EVENT (ORIGIN = @old_origin, CONFIRMED = @other_node);
> 
> MOVE SET ( ID = @set_to_move, OLD ORIGIN = @old_origin, NEW ORIGIN = @new_origin);
> WAIT FOR EVENT (ORIGIN = @old_origin, CONFIRMED = @new_origin);
> WAIT FOR EVENT (ORIGIN = @old_origin, CONFIRMED = @other_node);
> 
> 
> So for now everything is running, but what did I do wrong to leave node 3 still subscribed to node 1? 
> 
> What can I do to to move the subscription of node 3 over from noode 1 to 2?

I think you could just subscribe node 3 to node 2 :

subscribe set (id=@set_to_move, provider=@new_origin, receiver=@other_node,
forward=yes);


> 
> Any ideas would be very much appreciated, I'm a little worried at the moment, especially with the silence.
> 
> Thanks
> Glyn
> 
> 
> --- On Fri, 8/5/09, Glyn Astill <glynastill at yahoo.co.uk> wrote:
> 
>> From: Glyn Astill <glynastill at yahoo.co.uk>
>> Subject: Re: [Slony1-general] MOVE SET confusion
>> To: slony1-general at lists.slony.info
>> Date: Friday, 8 May, 2009, 12:14 PM
>> Ah, obviously it'd help if I stated this is 1.2.15
>>
>>
>> --- On Fri, 8/5/09, Glyn Astill
>> <glynastill at yahoo.co.uk> wrote:
>>
>>> From: Glyn Astill <glynastill at yahoo.co.uk>
>>> Subject: [Slony1-general] MOVE SET confusion
>>> To: slony1-general at lists.slony.info
>>> Date: Friday, 8 May, 2009, 10:51 AM
>>> Hi chaps,
>>>
>>> We have a setup with 3 nodes. Initially nodes 2 and 3
>> were
>>> subscribed to 1, but last night I moved the origin to
>> 2 as
>>> per the docs.
>>>
>>> All seems to be well, but I'm confused with what
>> the
>>> logs are showing. Node 1 has the following in it's
>> logs
>>> for each set;
>>>
>>> remoteWorkerThread_2: syncing set 2 with 43 table(s)
>> from
>>> provider 2
>>>
>>> But node 3 is saying this;
>>>
>>> remoteWorkerThread_2: syncing set 2 with 43 table(s)
>> from
>>> provider 1
>>>
>>> Surely when I moved the origin from node 1 to 2, both
>> nodes
>>> should be syncing from node 2?
>>>
>>> Anyone?
>>>
>>> Regards
>>> Glyn
>>>

Hope that helps.

Regards,
- --
Stéphane Schildknecht
PostgreSQLFr - http://www.postgresql.fr
Dalibo - http://www.dalibo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKCBSDA+REPKWGI0ERAtdnAJ4slyfzzgHeY2HjMLnD7rno8WmYmACdFpH2
MV9bZq2nXSgPXFymeO7Gb6s=
=Lq5L
-----END PGP SIGNATURE-----