<html><head></head><body><div class="ydpcb2de48dyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div><div dir="ltr" data-setdir="false">Hi Kirstine</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Something very confusing about pgpool is that when there is not enought child process available (i.e. there is no connection in the pool available for a new request) it does not give an error, it just queue the connection request and there is nothing in the log. </div><div dir="ltr" data-setdir="false">Furthermore the relation max_pool and num_init_children is not very clear and hard to understand unless you are in the easy case with a limited number of schema. </div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">So increasing num_init_children might indeed be the solution, especially if you see that your 40 child process are used.</div><div><br></div><div class="ydpcb2de48dsignature">Pierre</div></div>
<div><br></div><div><br></div>
</div><div id="ydpb496a32cyahoo_quoted_8968898837" class="ydpb496a32cyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Monday, September 9, 2019, 08:12:54 PM GMT+2, Travis Kirstine <tkirstine@firstbasesolutions.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydpb496a32cyiv0183747675">
<div dir="ltr">
<p>I have pgpool 3.4 running in front of a pg 9.4 two node cluster running in streaming replication mode with connection pooling. Under moderate load pgpool will become unresponsive and will need to be restarted. The system is being used with a PHP / Python
based web applications that can generate a number of concurrent selects / inserts (20 -100 queries per second). The database seems to be able to handle the load however pgpool will fail under stress. The database had 9 unique database / user combinations
and I have pgpool configured with:</p>
<p> </p>
<p>num_init_children = 40<br>
max_pool = 5<br>
child_life_time = 300<br>
child_max_connections = 0<br>
connection_life_time = 0<br>
client_idle_limit = 600</p>
<p><br>
</p>
<p>listen_backlog_multiplier = 10</p>
<p><br>
</p>
<p>Postgresql is configured with 250 max connections. I could increase the num_init_children and max_pool however I'm to sure if this would resolve the issue. The server supports up to 100,000 open files and appears to have around 15,000 open files when operational.<br>
</p>
<p><br>
</p>
<p>The issue I'm having is that it is not clear what could be causing the issue as there is no indication in the logs what is failing.<br>
</p>
<p><br>
</p>
<p>Any advise on how to trouble shoot this issue would be greatly appreciated <br>
</p>
<p><br>
<br>
</p>
<p><br>
</p>
<div id="ydpb496a32cyiv0183747675Signature">
<div style="font-family:Calibri, Arial, Helvetica, sans-serif;margin:0;">
</div>
</div>
</div>
</div>_______________________________________________<br>pgpool-general mailing list<br><a href="mailto:pgpool-general@pgpool.net" rel="nofollow" target="_blank">pgpool-general@pgpool.net</a><br><a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="nofollow" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br></div>
</div>
</div></body></html>