<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Sep 10, 2016 at 5:44 PM, Tory M Blue <span dir="ltr">&lt;<a href="mailto:tmblue@gmail.com" target="_blank">tmblue@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra">







<p><span>Running into an issue, working with a cluster on another network, so I added node 11 (insert secondary in site2) from node 2 (which is the insert secondary of site 1). Set 2 kept failing, so I went in and dropped node 11 from the cluster config, but node 2, which is the seecondary insert server continues with this error.. I&#39;ve not inserted anything into node 2, nor can you, I&#39;m really confused how my primary cluster got in this state..</span></p><p><span><br></span></p><p><span>Any assistance to help clean it up? Dropping node 2 and re-adding is a 24 hour ordeal.</span></p><p><span>2016-09-10 17:41:50 PDT ERROR  remoteWorkerThread_11: &quot;insert into &quot;_cls&quot;.sl_event     (ev_origin, ev_seqno, ev_timestamp,      ev_snapshot, ev_type     ) values (&#39;11&#39;, &#39;5000005698&#39;, &#39;2016-09-10 08:34:48.691123-07&#39;, &#39;6422065:6530984:6422065&#39;, &#39;SYNC&#39;); insert into &quot;_cls&quot;.sl_confirm <span>        </span>(con_origin, con_received, con_seqno, con_timestamp)    values (11, 2, &#39;5000005698&#39;, now()); select &quot;_cls&quot;.logApplySaveStats(&#39;_<wbr>cls&#39;, 11, &#39;0.047 s&#39;::interval); commit transaction;&quot; PGRES_FATAL_ERROR ERROR:  duplicate key value violates unique constraint &quot;sl_event-pkey&quot;</span></p>
<p><span>DETAIL:  Key (ev_origin, ev_seqno)=(11, 5000005698) already exists.</span></p><p><span></span></p></div></div></blockquote></div><br></div><div class="gmail_extra">Also interesting node 2 seems to think node 11 is still legit</div><div class="gmail_extra"><br></div><div class="gmail_extra">







<p class="gmail-p1"><span class="gmail-s1"><a href="http://idb01.prod.ca">idb01.prod.ca</a> is node 11:</span></p><p class="gmail-p1"><span class="gmail-s1"><a href="http://idb01.prod.ca.domain.net">idb01.prod.ca.domain.net</a> is not active. Make sure that it is already part of the slon configuration currently running</span></p><p class="gmail-p1"><span class="gmail-s1">







</span></p><p class="gmail-p1"><span class="gmail-s1">select * from _cls.sl_node;</span></p><p class="gmail-p1"><span class="gmail-s1"> no_id | no_active | no_comment | no_failed </span></p><p class="gmail-p1"><span class="gmail-s1">-------+-----------+------------+-----------</span></p><p class="gmail-p1"><span class="gmail-s1">     3 | t         | Node  3    | f</span></p><p class="gmail-p1"><span class="gmail-s1">     4 | t         | Node  4    | f</span></p><p class="gmail-p1"><span class="gmail-s1">     5 | t         | Node  5    | f</span></p><p class="gmail-p1"><span class="gmail-s1">     1 | t         | Node  1    | f</span></p><p class="gmail-p1"><span class="gmail-s1">     2 | t         | Node  2    | f</span></p><p class="gmail-p1">















</p><p class="gmail-p1"><span class="gmail-s1"> <b>   11 | t         | Node  11   | f</b></span></p><p class="gmail-p1"><span class="gmail-s1"><br></span></p><p class="gmail-p1"><span class="gmail-s1">Paths are there as well..</span></p><p class="gmail-p1"><span class="gmail-s1"><br></span></p><p class="gmail-p1"><span class="gmail-s1">Tory</span></p></div></div>