Andrew Sullivan wrote:
> On Tue, Aug 28, 2007 at 05:22:23PM +0200, Cyril SCETBON wrote:
>   
>>> Just change its origin.  This feature is one of the original design
>>> goals.
>>>  
>>>       
>> How do you make it ? MOVE SET can't do it cause the real Origin of SET 1 
>> is M1, not M2.
>>     
>
> You have to perform FAILOVER.  It means you abandon the node for
> good (and have to rebuild it when it comes back).
>   
In order to not break my configuration I'm reshaping subscription from 
S2 (node 4) to M1 (node 1), but
something weird is happening :

If I stop slon on node M2 and insert one line in a table on M1 before 
reshaping subscription from S2, S2 does not resync with M1 :-(

See it :

psql db1 -c 'select * from "_CLUSTER1".sl_subscribe'
 sub_set | sub_provider | sub_receiver | sub_forward | sub_active
---------+--------------+--------------+-------------+------------
       1 |            1 |            3 | t           | t
       1 |            1 |            2 | t           | t
       1 |            3 |            4 | t           | t

kill slon on M2 (provider=3)

db1=# INSERT INTO t1 
VALUES('DLJIEXKBQNMFLLTYLPYVXKFYFWXWGWIJRFNQRGIOLIDRSSNOZLWLHL');

provider=1=db1

reshaping subscriptions from s2 to M1 (with command subscribe set)

psql db1 -c 'select * from "_CLUSTER1".sl_subscribe'
 sub_set | sub_provider | sub_receiver | sub_forward | sub_active
---------+--------------+--------------+-------------+------------
       1 |            1 |            3 | t           | t
       1 |            1 |            2 | t           | t
       1 |            1 |            4 | t           | t

for i in `seq 1 4`; do echo db$i - `psql db$i -c 'select count(1) from 
t1'|grep -v [a-zA-Z]`; done
db1 - -------- 210037
db2 - -------- 210037
db3 - -------- 210036
db4 - -------- 210036

if I restart slon on node 3 everything works better :-(

for i in `seq 1 4`; do echo db$i - `psql db$i -c 'select count(1) from 
t1'|grep -v [a-zA-Z]`; donedb1 - -------- 210037
db2 - -------- 210037
db3 - -------- 210037
db4 - -------- 210037

I was thinking that as provider 1 didn't receive confirm from node 3 
(and of course from node 4) it will resend it to node 4 when node 4 
subscribe to provider 1. And if it's not, node 4 should resync with 
provider 1 to see if it missed events ?

Any explanation ? Is it a BUG ?


> A
>
>   

-- 
Cyril SCETBON - Ingénieur bases de données
AUSY pour France Télécom - SCR/HDI/DOP/HEBEX

Tél : +33 (0)4 97 12 87 60
Jabber : cscetbon at jabber.org
France Telecom - Orange
790 Avenue du Docteur Maurice Donat 
Bâtiment Marco Polo C2 
06250 Mougins
France

***********************************
Ce message et toutes les pieces jointes (ci-apres le 'message') sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration. Le Groupe France
Telecom decline toute responsabilite au titre de ce message s'il a ete
altere, deforme ou falsifie.
Si vous n'etes pas destinataire de ce message, merci de le detruire
immediatement et d'avertir l'expediteur.
***********************************
This message and any attachments (the 'message') are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. France Telecom Group shall not be
liable for the message if altered, changed or falsified.
If you are not recipient of this message, please cancel it immediately and
inform the sender.
************************************