<div dir="ltr">yes... that's it!!</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 4, 2016 at 8:58 AM, Tignor, Tom <span dir="ltr"><<a href="mailto:ttignor@akamai.com" target="_blank">ttignor@akamai.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div><br>
</div>
<div><span style="white-space:pre-wrap"></span>If I’m reading right, did you run the drop node op at some point on node 1 and see it succeed? If it did, the sl_node table on each other node in the cluster (save perhaps node 3) should show
it gone.</div>
<div><span style="white-space:pre-wrap"></span>If that’s the case, your cluster is fine and you can just run ‘DROP SCHEMA mycluster CASCADE’ on node 3 and then retry your store node script.</div>
<div><br>
</div>
<div><span style="white-space:pre-wrap"></span>Tom :-)</div>
<div><br>
</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Sung Hsin Lei <<a href="mailto:sungh.lei@gmail.com" target="_blank">sungh.lei@gmail.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, February 3, 2016 at 11:37 PM<br>
<span style="font-weight:bold">To: </span>slony <<a href="mailto:slony1-general@lists.slony.info" target="_blank">slony1-general@lists.slony.info</a>><br>
<span style="font-weight:bold">Subject: </span>[Slony1-general] Cannot fully drop slony node<br>
</div><div><div class="h5">
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hey guys,
<div><br>
</div>
<div>I have a cluster with 3 nodes. On the main db, I run the following script:</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>cluster name = slony_cluster;</div>
<div><br>
</div>
<div>node 1 admin conninfo = 'dbname = dbNAME host = localhost user = slonyuser password = slonPASS port = 5432';</div>
<div>node 3 admin conninfo = 'dbname = dbNAME host = 172.16.10.4 user = slonyuser password = slonPASS port = 5432';</div>
<div><br>
</div>
<div>DROP NODE ( ID = 3, EVENT NODE = 1 );</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>I open pdadmin on the main db and I don't see node 3 anymore. However, when I open pgadmin on the replicated db, I still see node 3. The replicated db is the one associated with node 3. I run the above script again on the replicated db but get the following
error:</div>
<div><br>
</div>
<div>
<div><br>
</div>
<div>C:\Program Files\PostgreSQL\9.3\bin>slonik drop.txt</div>
<div>debug: waiting for 3,5000000004 on 1</div>
<div>drop.txt:4: PGRES_FATAL_ERROR lock table "_slony_securithor2".sl_event_lock, "_s</div>
<div>lony_cluster".sl_config_lock;select "_slony_securithor2".dropNode(ARRAY[3]);</div>
<div> - ERROR: Slony-I: DROP_NODE cannot initiate on the dropped node</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>Now I need to setup another node which must have id=3. I run a script on the main db(the one pgadmin does not show a node 3). The following is the script that I used to setup the node and the error that I get:</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>cluster name = slony_cluster;</div>
<div><br>
</div>
<div>node 1 admin conninfo = 'dbname = dbNAME host = localhost user = slonyuser password = slonPASS port = 5432';</div>
<div>node 3 admin conninfo = 'dbname = dbNAME host = 172.16.10.4 user = slonyuser password = slonPASS port = 5432';</div>
<div><br>
</div>
<div>store node (id=3, comment = 'Slave node 3', event node=1);</div>
<div>store path (server = 1, client = 3, conninfo='dbname=dbNAME host=172.16.10.3 user=slonyuser password = slonPASS port = 5432');</div>
<div>store path (server = 3, client = 1, conninfo='dbname=dbNAME host=172.16.10.4 user=slonyuser password = slonPASS port = 5432');</div>
<div><br>
</div>
<div>subscribe set ( id = 1, provider = 1, receiver = 3, forward = no);</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>C:\Program Files\PostgreSQL\9.3\bin>slonik create.txt</div>
<div>drop.txt:6: Error: namespace "_slony_cluster" already exists in database of</div>
<div>node 3</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div><br>
</div>
<div>Is there another way to drop nodes? Can I recover from this without dropping the cluster and restarting from scratch?</div>
<div><br>
</div>
<div><br>
</div>
<div>Thanks.</div>
</div>
</div>
</div>
</div></div></span>
</div>
</blockquote></div><br></div>