<div dir="ltr"><div class="gmail_extra">
<p class="gmail-p1"><span class="gmail-s1">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've not inserted anything into node 2, nor can you, I'm really confused how my primary cluster got in this state..</span></p><p class="gmail-p1"><span class="gmail-s1"><br></span></p><p class="gmail-p1"><span class="gmail-s1">Any assistance to help clean it up? Dropping node 2 and re-adding is a 24 hour ordeal.</span></p><p class="gmail-p1"><span class="gmail-s1">2016-09-10 17:41:50 PDT ERROR remoteWorkerThread_11: "insert into "_cls".sl_event (ev_origin, ev_seqno, ev_timestamp, ev_snapshot, ev_type ) values ('11', '5000005698', '2016-09-10 08:34:48.691123-07', '6422065:6530984:6422065', 'SYNC'); insert into "_cls".sl_confirm <span class="gmail-Apple-tab-span"> </span>(con_origin, con_received, con_seqno, con_timestamp) values (11, 2, '5000005698', now()); select "_cls".logApplySaveStats('_cls', 11, '0.047 s'::interval); commit transaction;" PGRES_FATAL_ERROR ERROR: duplicate key value violates unique constraint "sl_event-pkey"</span></p>
<p class="gmail-p1"><span class="gmail-s1">DETAIL: Key (ev_origin, ev_seqno)=(11, 5000005698) already exists.</span></p><p class="gmail-p1"><span class="gmail-s1"><br></span></p><p class="gmail-p1"><span class="gmail-s1">thanks</span></p><p class="gmail-p1"><span class="gmail-s1">Tory</span></p></div></div>