Mon Feb 8 12:19:49 PST 2010
- Previous message: [Slony1-general] Any reason not to have 2 replication slaves, replicating to the same query slave
- Next message: [Slony1-general] dropping a forwarder
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
So after last weeks discussion I'm still running into issues trying to
remove a forwarder and replace it with another forwarder talking to
the remaining replica.
To keep things simple.
1-2
1-3
2-4
Set 1
Want to remove the forwarder (2), and since the origin is not moving,
doesn't seem a fail-over or switchover fits the bill here.
I've tried to simply drop the path of 2 and run a simple subscribe set
( id=1, provider=3, receiver=4); but the replica seems to get
confused and without restarting slony on the replica things don't
seem to ever catch up.
Since I'm not replacing the origin and just a forwarder, are there
steps that I should be doing vs just issuing a subscribe to another
forwarder?, I don't want to unsubscribe, I just want the replica to
get it's updates from forwarder (3) now.
When i drop node 2, here is what I've tried.
SLONIK_COMMANDS="$SLONIK_COMMANDS
SUBSCRIBE SET ( ID = 1, PROVIDER = 3, RECEIVER = 4, forward = no);
WAIT FOR EVENT ( ORIGIN = 3, CONFIRMED = 4 ) ; <-- run with and without
UNSUBSCRIBE SET ( ID = 1, RECEIVER = 2);
DROP PATH ( SERVER = 2, CLIENT = 4 );
DROP PATH ( SERVER = 4, CLIENT = 2 );
DROP PATH ( SERVER = 1, CLIENT = 2 );
DROP PATH ( SERVER = 2, CLIENT = 1 );
This sometimes works and other times does not, again it seems if I
restart the replica (4) things are happy, but I feel that there is
something I'm doing wrong, or out of order?
Thanks again
Tory
- Previous message: [Slony1-general] Any reason not to have 2 replication slaves, replicating to the same query slave
- Next message: [Slony1-general] dropping a forwarder
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list