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

Le 23/08/2010 21:50, Steve Singer a écrit :
> Stéphane A. Schildknecht wrote:
> 
> What you describe might not be a bug.
> 
> What should happen in a move set (at a high level) is
> 
> 1. Slonik contacts the origin and executes moveSet()
> 2. moveSet() sets all the tables to read only
> 3. moveSet() creates a MOVE_SET event
> 4. moveSet() exists -- this is what you see in the log
> 5. The MOVE_SET event travels to subscribers through replication paths
> and these subscribers reconfigure themselves.  The new origin will
> reconfigure itself when it receives the MOVE_SET command as well.
> 
> The set isn't 'moved' until the move set command is confirmed by all nodes.

Hi Steve,

Thanks for your answer.

What really surprised me, is that I've already done such moves, and it was
always really quick. That time, after a couple of minutes, the situation still
remains with all tables in read-only on every nodes.
Maybe I should have waited for a longer piece of time...

Best regards,
Stéphane Schildknecht
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxzhBgACgkQA+REPKWGI0FZTACg3dkmEjthJPrYAFe9eBaJToyj
QecAn05VclS7a4ToT+FnzXzfCzdUqyA7
=OwH6
-----END PGP SIGNATURE-----