On 10-12-19 02:14 AM, Scott Marlowe wrote:
> So, I've got a 5 node system, and some of the nodes have entries for a
> test set, and some don't. The "control" or local machine does not.
> when running drop set I get the error
>
I'm not sure what you mean by "control" node.
Which node is the origin of the set your trying to drop? Is it node 6?
What is in sl_set on node 6? The origin parameter drop DROP SET should
be the set origin.
> Slonik script:
>
> cluster name = slony_www;
> node 6 admin conninfo='host=db6 dbname=www user=slony port=5432';
>
> cluster name = slony_www;
> node 6 admin conninfo='host=db6 dbname=www user=slony port=5432';
> node 7 admin conninfo='host=db7 dbname=www user=slony port=5432';
> node 3 admin conninfo='host=db7 dbname=www user=slony port=5433';
> node 1 admin conninfo='host=db1 dbname=www user=slony port=5432';
> node 2 admin conninfo='host=db2 dbname=www user=slony port=5432';
>
> echo 'Dropping set 204';
> try {
> drop set (id = 204, origin = 6);
> }
> on error {
> exit 1;
> }
> echo 'Dropped Set 204';
>
>
> <stdin>:5: PGRES_FATAL_ERROR select "_slony_www".dropSet(204); -
> ERROR: Slony-I: set 204 does not originate on local node
>
> The entry for the 204 set is on nodes 6, 7, 3, and 1. Node 2 is the
> control node that is missing the entry.
>
> It takes somewhere on the order of a half a day to re-establish slony
> replication if I have to tear it all down and start over, so I'd like
> to just be able to drop this half-created set. But it won't go.
>
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
