<div dir="ltr">Hello,<div><br></div><div>What about triggering a replication lag check whenever a node passes a health check?</div><div><br></div><div>Cheers,</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div style="color:#b8276a;font:bold 14px Arial,Helvetica,sans-serif">
<br>
<span style="color:#323b62">James Sewell,</span><br>
<span style="color:#a9a9a9"><span style="font:12px Arial,Helvetica,sans-serif">PostgreSQL Team Lead / Solutions Architect </span></span><br>
<span style="color:#a9a9a9">______________________________________</span><br>
</div>
<img alt="" src="http://www.lisasoft.com/sites/lisasoft/files/u1/logo1.jpg" style="margin:0px;width:153px;height:50px"><br>
<div style="font:normal 12px/20px Arial,Helvetica,sans-serif;color:#404040;margin:0">
<span style="color:#a9a9a9">Level 2, 50 Queen St, Melbourne VIC 3000</span><br>
<br>
<strong>P </strong><span style="color:#a9a9a9"><span style="font-family:Arial,Verdana,sans-serif">(+61) 3 8370 8000</span></span><span style="color:rgb(169,169,169)"> </span><strong> </strong><span style="color:rgb(50,59,98)"><span style="width:15px;display:inline-block"><strong>W</strong></span></span> <a style="color:rgb(64,64,64);margin:2px 0px;text-decoration:none"><span style="color:#a9a9a9">www.lisasoft.com</span></a> <span style="color:rgb(50,59,98)"><span style="width:15px;display:inline-block"><strong>F </strong></span></span><span style="color:#a9a9a9"><span style="font-family:Arial,Verdana,sans-serif">(+61) 3 8370 8099</span></span></div>
<div style="padding-top:8px">
</div></div></div>
<br><div class="gmail_quote">On Mon, May 9, 2016 at 3:44 PM, Tatsuo Ishii <span dir="ltr"><<a href="mailto:ishii@postgresql.org" target="_blank">ishii@postgresql.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Hey All,<br>
><br>
> This looks like a great step forward for PGPool.<br>
><br>
> One question - would it be possible to set health_check_max_retries to a<br>
> value which means it will just keep retrying?<br>
><br>
><br>
> This way a node which was inactive for a longer period could still return<br>
> to service once it started responding.<br>
><br>
> Or perhaps there is another, better way to deal with this?<br>
<br>
</span>Hum. At the moment I can't think of a reason why this does not<br>
work. One thing I'm worrying is, the node which starts to respond is<br>
actually in a good state or not. If it's an outdated standby, users<br>
may get outdated data before pgpool notices that the standby delay is<br>
too much. Though I have to admit that this is an existing problem even<br>
if you do not try the large health_check_max_retries value. We need<br>
more rigorous checking with failback?<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
</blockquote></div><br></div>
<br>
<p><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:14.545454025268555px;background-color:rgb(255,255,255)"><hr><font size="1" color="Gray" face="Arial">The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.</font></div></p>