<p dir="ltr"><i>> What version of pgpool-II is this?</i><br>
<i>></i></p>
<p dir="ltr">It's 3.3.6</p>
<div class="gmail_quote">El 24/03/2016 00:54, "Tatsuo Ishii" <<a href="mailto:ishii@postgresql.org">ishii@postgresql.org</a>> escribió:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What version of pgpool-II is this?<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>
<br>
> Hello!<br>
><br>
> I was doing online recovery with 2 PSQL nodes and Pgpool configured with<br>
> "replication_mode = on".<br>
><br>
> Every test I made recovering one PSQL node was succesful, but now I tried<br>
> to recover a bigger database (20 GB).<br>
><br>
> 1st stage was made OK:<br>
><br>
> - Put active psql node with WAL archiving.<br>
> - Send pg_start_backup<br>
> - Compress all PGDATA<br>
> - Send pg_stop_backup<br>
> - Remove WAL archiving<br>
> - Transfer tar.gz to failed node (3 GB size)<br>
><br>
> pid 12936: 1st stage is done<br>
> pid 12936: starting 2nd stage<br>
><br>
> - Now pgpool closes connections without waiting to finish queries (I<br>
> configured that way).<br>
><br>
> pid 12728: pool_process_query: child connection forced to terminate due to<br>
> client_idle_limitis -1<br>
> ...<br>
> ...<br>
> pid 12817: pool_process_query: child connection forced to terminate due to<br>
> client_idle_limitis -1<br>
><br>
> And then:<br>
><br>
> ERROR: pid 12936: wait_connection_closed: existing connections did not<br>
> close in 90 sec.<br>
> ERROR: pid 12936: start_recovery: timeover for waiting connection closed<br>
><br>
><br>
> Why pgpool couldn't close a PSQL connection ?<br>
><br>
><br>
> Thanks.<br>
</blockquote></div>