<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 24 August 2015 at 17:03, Steve Singer <span dir="ltr"><<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</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"><span class="">On 08/24/2015 04:58 PM, Dave Cramer wrote:<br>
</span><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"><span class="">
<br>
On 24 August 2015 at 16:57, Steve Singer <<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a><br></span><span class="">
<mailto:<a href="mailto:ssinger@ca.afilias.info" target="_blank">ssinger@ca.afilias.info</a>>> wrote:<br>
<br>
On 08/24/2015 04:12 PM, Dave Cramer wrote:<br>
<br>
I am currently waiting on a resubscribe event. How does slony<br>
get this<br>
event through all the backlog events ?<br>
<br>
<br>
Usually pretty quickly.<br>
Slonik waits for the provider to be caught up before submitting the<br>
event.<br>
<br>
The question is, why is your provider behind? Is it getting caught up?<br>
<br>
<br>
I presumed it was behind because one node was missing and this was<br>
blocking replication.<br>
<br>
Note the nodes are chained 1->2, 2->3, 3-4. 3 is the one that failed<br>
<br>
</span></blockquote>
<br>
<br>
and a slonik script like<br>
---------------<br>
cluster name=mycluster;<br>
node 1 admin conninfo='...'<br>
node 4 admin conninfo='...'<br>
<br>
resubscribe node(origin=1,provider=1,receiver=4);<br>
----------<br>
<br>
is waiting?<br>
<br>
If so it should tell you from which node it is waiting for events from.<br></blockquote><div><br></div><div>Close enough. I went from 2 to 4 and this is the output</div><div><br></div><div>waiting for events (4,5002587214) only at (4,5002579907) to be confirmed on node 2</div><div> </div><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">
<br>
<br>
<br>
<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"><span class="">
<br>
<br>
Dave Cramer<br>
<br>
On 24 August 2015 at 15:38, Scott Marlowe<br>
<<a href="mailto:scott.marlowe@gmail.com" target="_blank">scott.marlowe@gmail.com</a> <mailto:<a href="mailto:scott.marlowe@gmail.com" target="_blank">scott.marlowe@gmail.com</a>><br></span>
<mailto:<a href="mailto:scott.marlowe@gmail.com" target="_blank">scott.marlowe@gmail.com</a><span class=""><br>
<mailto:<a href="mailto:scott.marlowe@gmail.com" target="_blank">scott.marlowe@gmail.com</a>>>> wrote:<br>
<br>
Note that the node will still show up in sl_nodes and<br>
sl_status for a<br>
while, until slony does a cleanup event / log switch (can't<br>
remember<br>
which right now). This is normal. Don't freak out.<br>
<br>
<br>
<br>
<br>
</span></blockquote>
<br>
</blockquote></div><br></div></div>