<div dir="ltr">Another thing that I noticed is that there is only one slon process running for node 3 instead of two.<div><br></div><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 2:55 PM, Granthana Biswas <span dir="ltr"><<a href="mailto:granthana.biswas@gmail.com" target="_blank">granthana.biswas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Also the nodelock table on node1 and 2 have too many rows for node 3:<div><br></div><div><div>select count(*) from "_cluster".sl_nodelock where nl_nodeid =3;</div><div> count </div><div>-------</div><div> 67</div><div><div class="h5"><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 30, 2014 at 2:29 PM, Granthana Biswas <span dir="ltr"><<a href="mailto:granthana.biswas@gmail.com" target="_blank">granthana.biswas@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi All,<div><br></div><div>My replication setup is as db1 -> db2 -> db3.</div><div><br></div><div>On adding a new set to the cluster, the merge from node 3 is going on waiting state for node 3 to subscribe. Because of this, node 3 is lagging behind.</div><div><br></div><div>These are the slonik commands that I used to add new set, subscribe and merge:</div><div>---------------------------------------------------------------------------------------------------------</div><div><div>create set ( id = 2, origin = 1, comment = 'replication set for surcharge table');</div><div><br></div><div>set add table (set id = 2, origin = 1, id = 1744, fully qualified name = 'public.t2', comment = 't2 table');</div><div>set add sequence (set id = 2, origin = 1, id = 1756, fully qualified name = 'public.s2', comment = 's2 sequence');</div><div><br></div><div>subscribe set ( id = 2, provider = 1, receiver = 2, forward = yes );</div><div>subscribe set ( id = 2, provider = 2, receiver = 3, forward = yes );</div><div><br></div><div>merge set ( id = 1, add id = 2, origin = 1);</div></div><div>-----------------------------------------------------------------------------------------------------------</div><div><br></div><div>Even though it goes it waiting mode, the sl_subscribe table shows the following:</div><div><br></div><div><div> sub_set | sub_provider | sub_receiver | sub_forward | sub_active </div><div>---------+--------------+--------------+-------------+------------</div><div> 1 | 1 | 2 | t | t</div><div> 1 | 2 | 3 | t | t</div><div> 2 | 1 | 2 | t | t</div><div> 2 | 2 | 3 | t | t</div></div><div><br></div><div><br></div><div>But the slony log on node 3 shows the following repeatedly:</div><div><br></div><div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=29117</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=30115</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=30116</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=30414</div><div>NOTICE: Slony-I: Logswitch to sl_log_2 initiated</div><div>CONTEXT: SQL statement "SELECT "_cluster".logswitch_start()"</div><div>PL/pgSQL function "cleanupevent" line 96 at PERFORM</div><div>NOTICE: truncate of <NULL> failed - doing delete</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=31364</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=31369</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=31368</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=32300</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=1117</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=1149</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=1186</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=1247</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=1270</div><div>NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=1294</div></div><div><br></div><div><br></div><div>It is continuously trying to cleanup stale nodelock entry for nl_nodeid=3 and nl_conncnt=0.</div><div><br></div><div>I tried stopping and starting the slon process for node 3 which didn't help. I don't see any errors in the other slony log files.</div><div><br></div><div>Do I have to stop all slon processes of all nodes and start again?</div><div><br></div><div>Regards,</div><div>Granthana</div></div>
</blockquote></div><br></div></div></div></div></div>
</blockquote></div><br></div></div></div>