Wed Feb 27 04:55:42 PST 2008
- Previous message: [Slony1-general] Failover problem
- Next message: [Slony1-general] Failover problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 27 Feb 2008 13:30:05 +0100, Sebastien Lardiere <sebastien at lardiere.net> wrote: > > On Wed, 27 Feb 2008 12:53:35 +0100, "Stéphane A. Schildknecht" > <stephane.schildknecht at postgresqlfr.org> wrote: >>> >>> Before failover, i've got : >>> >>> >>> bar=# select * from _qsr_repl.sl_subscribe ; >>> sub_set | sub_provider | sub_receiver | sub_forward | sub_active >>> ---------+--------------+--------------+-------------+------------ >>> 1 | 1 | 2 | f | t >>> 1 | 1 | 3 | f | t >>> (2 rows) >>> >>> And after too, because failover fail, and so nothing is done. >> >> >> Shouldn't node 2 and/or 3 be forwarder if you want to use one of them as > a >> master ? > > You're right, i enable forward for 2 and 3, and then failover work. > > On 2, it's ok : > > infoctr=# select * from _qsr_repl.sl_subscribe ; > sub_set | sub_provider | sub_receiver | sub_forward | sub_active > ---------+--------------+--------------+-------------+------------ > 1 | 2 | 3 | t | t > (1 row) > > > But on 3 , I've got a problem : > > infoctr=# SELECT * from _qsr_repl.sl_subscribe ; > sub_set | sub_provider | sub_receiver | sub_forward | sub_active > ---------+--------------+--------------+-------------+------------ > 1 | 3 | 2 | t | t > 1 | 2 | 3 | t | t > > And replication doesn't work anymore > Well, i think that node 3 doesn't apply "drop node" about node 1, so always know node1. Node 2, the new master, doesn't have any info about node 1 anymore ... -- Sébastien
- Previous message: [Slony1-general] Failover problem
- Next message: [Slony1-general] Failover problem
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list