[pgpool-general: 4226] Re: child process with pid: ## exits with status 512 / fork a new child process with pid: #

[Ziyun Audrey Wang]

Hi

Thanks for your quick answer.

We have the child_max_connections = 0

child_max_connections = 0
                                   # Pool exits after receiving that many connections
                                   # 0 means no exit

Not sure if this means we have reached the max number of connections that we need to increase some of the parameter value?

But don’t know which parameter should be tuned?

We currently have the following:

num_init_children = 512
max_pool = 4

child_life_time = 300
child_max_connections = 0
connection_life_time = 0

client_idle_limit = 0

connection_cache = off


in postgres, the max_connections=1024


Thanks!

Audrey


From: Muhammad Usama [mailto:m.usama at gmail.com]
Sent: November-19-15 7:27 AM
To: Ziyun Audrey Wang
Cc: pgpool-general at pgpool.net
Subject: Re: [pgpool-general: 4219] child process with pid: ## exits with status 512 / fork a new child process with pid: #

Hi

Normally pgpool-II child process exits with this status code when the child is terminated because of child max connections.
This is normal behaviour and it can be controlled by pgpool's child_max_connections configuration parameter.


Thanks
Best regards
Muhammad Usama



On Tue, Nov 17, 2015 at 6:38 PM, Ziyun Audrey Wang <ziyun.wang at ericsson.com<mailto:ziyun.wang at ericsson.com>> wrote:
Hello,

We have seen a lots of messages in the pgpool log about:

child process with pid: ## exits with status 512 / fork a new child process with pid: #

we are not sure if this is normal.
When it exit with status 512.

Thanks!

Best Regards

Audrey



_______________________________________________
pgpool-general mailing list
pgpool-general at pgpool.net<mailto:pgpool-general at pgpool.net>
http://www.pgpool.net/mailman/listinfo/pgpool-general

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20151119/6963d4f5/attachment.html>