<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Feb 15, 2014 at 10:48 PM, Jeff Frost <span dir="ltr"><<a href="mailto:jeff@pgexperts.com" target="_blank">jeff@pgexperts.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">It's probably a firewall timing out your PostgreSQL connection while the indexes are being built on the replica.<br>
<br>
Look into tcp keep alive settings.<br>
<br></blockquote><div><br></div><div>Yes this is what I thought it was when I first started with this, but didn't make any progress. Keepalives by default is set to 7200 seconds, so 2 hours, this is failing in an hour, so I'll have to look at the firewalls between us but since I'm connected to these boxes the entire time, from the same network that is originating the slon configuration, I'm doubting the firewalls are reaping the connections.</div>
<div><br></div><div>Looking at the TCP keepalive settings, I don't think there is any tuning there that can help</div><div><br></div><div><div>net.ipv4.tcp_keepalive_time = 7200</div><div>net.ipv4.tcp_keepalive_probes = 9</div>
<div>net.ipv4.tcp_keepalive_intvl = 75</div></div><div><br></div><div>Well, maybe I can "reduce this" just to make some interesting traffic happen within that hour+ that the indexes are being created.</div><div>
<br></div><div>Hmmm maybe.</div><div><br></div><div>Tory</div></div></div></div>