<div dir="ltr">Oh I forgot the configuration, here it is :<div><br></div><div><div>health_check_period = 2</div><div>health_check_timeout = 6</div><div>health_check_max_retries = 0</div><div>health_check_retry_delay = 1</div><div>connect_timeout = 10000</div></div><div><br></div><div>No individual healtcheck settings.</div><div><br></div><div>So of course I could increase
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">connect_timeout</span>, but 10 seconds is already a lot to trigger failover process for a production server receiving ~10 insert / second.</div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-04-26 21:23 GMT+02:00 Bud Curly <span dir="ltr"><<a href="mailto:psyckow.prod@gmail.com" target="_blank">psyckow.prod@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi and thanks for your work.</div><div><br></div><div>I use pgpool2 3.7.2 (latest git) with 2 backend as master-slave mode with native stream replication.</div><div><br></div><div>I think I have an issue concerning the health check process.</div><div><br></div><div>Since two days now I had two "health check timer expired" that appears yersterday around 9 am and today around 8 pm.</div><div><br></div><div>The weird thing is... Pgpool and the backend in question are on the same machine. This backend is the master. Here is the log :</div><div><br></div><div><div>2018-04-26 20:59:29: pid 2153:LOG: failed to connect to PostgreSQL server on "x.x.x.x:xxx" using INET socket</div><div>2018-04-26 20:59:29: pid 2153:DETAIL: health check timer expired</div><div>2018-04-26 20:59:29: pid 2153:ERROR: failed to make persistent db connection</div><div>2018-04-26 20:59:29: pid 2153:DETAIL: connection to host:"
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">x.x.x.x:xxx</span>" failed</div><div>2018-04-26 20:59:29: pid 2153:LOG: health check failed on node 0 (timeout:1)</div><div>2018-04-26 20:59:29: pid 2153:LOG: received degenerate backend request for node_id: 0 from pid [2153]</div><div>2018-04-26 20:59:29: pid 2104:LOG: Pgpool-II parent process has received failover request</div><div>2018-04-26 20:59:29: pid 2104:LOG: starting degeneration. shutdown host
<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">x.x.x.x:xxx</span> </div><div>2018-04-26 20:59:29: pid 2104:LOG: Restart all children</div></div><div><br></div><div>Despite the fact that these are on the same machine, I use public IP for the backend0 and not 127.0.0.1, because of failover process that required this ip.</div><div><br></div><div>Do you think this could be a problem from network conditions on the server itself or an actual issue ?</div><div><br></div><div>Thanks</div></div>
</blockquote></div><br></div>