<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
        {page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>I’ve had something very odd happen. I’m not sure
what caused the issue so I’ll try giving some background.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>We have a cluster of 4 servers – 2 local (nodes 1
& 2) and 2 remote (3 & 4). Awhile ago we wanted to try a pseudo-test of
our failover strategies and so cut our VPN connection to the co-location and
had it begin to operate in failover mode. This meant the 2 servers here were
continuing to replicate in their cluster and the 2 remote were now operating in
their own cluster. Generally things went as planned, we learned some things,
and plotted out some changes.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I then removed the slony cluster information from the remote
servers.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Today we brought the VPN link back up and I went about
adding the remote servers back into the cluster. We have a few different DBs,
each with their own clusters, and one of them has a very large table that takes
several hours to copy. To be efficient, after getting everything listening
right, I subscribed to all the sets *<b>except</b>* the one with the very large
table. I then made sure all the other clusters were working properly. Things
all seemed good.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>So I came back and subscribed node 3 to set 8 (the one with
the big table), with node 1 as the provider.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Things looked fine. Slonik script executed, no errors, but
then things seemed to happen too quick – a matter of seconds instead of
hours – so I took a closer look. Everything says node 3 is subscribed to
node 8, but when I look at sl_table and sl_sequence on node 3, there’s no
tables or sequences listed for node 8. The only thing I see in the log is:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>DEBUG2 remoteWorkerThread_1: syncing set 8 with 0 table(s)
from provider 1<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Now, this set is replicating properly between node 1 and
node 2. I have verified that. So, what could cause it to end up like this on
node 3? <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>I have tried unsubscribing the node and re-subscribing but
that didn’t help.<o:p></o:p></p>
</div>
</body>
</html>