<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 3, 2016 at 2:07 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">Usama,<br>
<br>
Can you please add this to our FAQ? I bet we will have similar<br>
questions over and over in the future. Registering this to FAQ saves<br>
both users and developers time a lot.<br></blockquote><div><br></div><div>I have updated the FAQ page with this information. </div><div><br></div><div>Regards</div><div>Muhammad Usama</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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>
<div class="HOEnZb"><div class="h5"><br>
> On Wed, Mar 2, 2016 at 12:52 AM, Burton, Chuck <<a href="mailto:Chuck.Burton@arris.com">Chuck.Burton@arris.com</a>><br>
> wrote:<br>
><br>
>> We are running pgpool in our lab in a virtualized, dockerized environment<br>
>> with pgpool managing two streaming replicated Postgres nodes. I am running<br>
>> pgpool 3.5.0.1.<br>
>><br>
>><br>
>><br>
>> I am using pgbench to connect through pgpool:<br>
>><br>
>><br>
>><br>
>> /usr/pgsql-9.3/bin/pgbench -c 300 -r -j 5 -t 3334 -h pgpool -p 9999 dbname<br>
>><br>
>><br>
>><br>
>> What is happening is I’m getting frequent disconnects of the pcp worker:<br>
>><br>
>><br>
>><br>
>> 2016-03-01 19:36:48: pid 5369: LOG: forked new pcp worker, pid=7377<br>
>> socket=7<br>
>><br>
>> 2016-03-01 19:36:48: pid 5369: LOG: PCP process with pid: 7377 exit with<br>
>> SUCCESS.<br>
>><br>
>> 2016-03-01 19:36:48: pid 5369: LOG: PCP process with pid: 7377 exits with<br>
>> status 0<br>
>><br>
>> 2016-03-01 19:36:48: pid 244: LOG: reload config files.<br>
>><br>
>> 2016-03-01 19:36:48: pid 5370: LOG: reloading config file<br>
>><br>
>> 2016-03-01 19:37:00: pid 5369: LOG: forked new pcp worker, pid=7433<br>
>> socket=7<br>
>><br>
>> 2016-03-01 19:37:00: pid 5369: LOG: PCP process with pid: 7433 exit with<br>
>> SUCCESS.<br>
>><br>
>> 2016-03-01 19:37:00: pid 5369: LOG: PCP process with pid: 7433 exits with<br>
>> status 0<br>
>><br>
>> 2016-03-01 19:37:00: pid 244: LOG: reload config files.<br>
>><br>
>> 2016-03-01 19:37:03: pid 5370: LOG: reloading config file<br>
>><br>
><br>
> This is the normal life cycle of PCP command in pgpool-II 3.5. Previously<br>
> pgpool-II could only handle single PCP command at a time and all PCP<br>
> commands were handled by a single PCP child process which lives throughout<br>
> the lifespan of pgpool-II main process.<br>
> This is now changed in the latest version 3.5. Now for every PCP command<br>
> issued to pgpool a new PCP child process is forked and that process exits<br>
> after execution of that PCP command is complete. So the LOG contains the<br>
> messages about the creation and exit of a PCP worker process, which is<br>
> perfectly normal.<br>
><br>
><br>
>><br>
>> Also, occasionally:<br>
>><br>
>><br>
>><br>
>> 2016-03-01 19:36:18: pid 4497: FATAL: Backend throw an error message<br>
>><br>
>> 2016-03-01 19:36:18: pid 4497: DETAIL: Exiting current session because of<br>
>> an error from backend<br>
>><br>
>> 2016-03-01 19:36:18: pid 4497: HINT: BACKEND Error: "function<br>
>> pgpool_regclass(unknown) does not exist"<br>
>><br>
><br>
> This error message suggests that pgpool_regclass extension is not installed<br>
> on the PostgreSQL backend.<br>
> <a href="http://www.pgpool.net/mediawiki/index.php/FAQ#Why_do_I_need_to_install_pgpool_regclass.3F" rel="noreferrer" target="_blank">http://www.pgpool.net/mediawiki/index.php/FAQ#Why_do_I_need_to_install_pgpool_regclass.3F</a><br>
><br>
> Regards<br>
> Muhammad Usama<br>
><br>
><br>
>><br>
>> This happened six times during the five-minute pgbench test.<br>
>><br>
>><br>
>><br>
>> I am running with:<br>
>><br>
>><br>
>><br>
>> num_init_children = 1000<br>
>><br>
>> # Number of pools<br>
>><br>
>> # (change requires restart)<br>
>><br>
>> max_pool = 1<br>
>><br>
>> # Number of connections per pool<br>
>><br>
>> # (change requires restart)<br>
>><br>
>> listen_backlog_multiplier = 3<br>
>><br>
>> serialize_accept = on<br>
>><br>
>> child_life_time = 0<br>
>><br>
>><br>
>><br>
>> Is this a problem with the pcp worker getting overwhelmed?<br>
>><br>
>><br>
>><br>
>> Looking at the new metrics on show pool_nodes I see that reads are being<br>
>> distributed.<br>
>><br>
>> _______________________________________________<br>
>> pgpool-general mailing list<br>
>> <a href="mailto:pgpool-general@pgpool.net">pgpool-general@pgpool.net</a><br>
>> <a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" rel="noreferrer" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
>><br>
>><br>
</div></div></blockquote></div><br></div></div>