<div dir="ltr">Thanks Tatsuo<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Dec 31, 2019 at 3:38 PM Tatsuo Ishii <<a href="mailto:ishii@sraoss.co.jp">ishii@sraoss.co.jp</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">First of all, 3.3.4 is not maintained any more. Please use Pgpool-II<br>
versions maintained by community. (see<br>
<a href="https://pgpool.net/mediawiki/index.php/EOL_information" rel="noreferrer" target="_blank">https://pgpool.net/mediawiki/index.php/EOL_information</a> more info on<br>
EOL).<br>
<br>
I see you use repmgr which in my understanding it does failover, while<br>
Pgpool-II does failover as well. So I suspect there might be conflict<br>
between them in terms of failover.<br>
<br>
>From what I understand, Pgpool-II surely detects connection problem<br>
with standby. Maybe repmgr does something to standby which makes<br>
Pgpool-II thinks that there's a problem with standby?<br>
<br>
> Thanks Tatsuo<br>
> <br>
> here is the reply:<br>
> 1- pgpool-II version 3.3.4 (tokakiboshi)<br>
> 2- psql -U pgpool --dbname=postgres --host 10.10.0.2 -c "show pool_nodes"<br>
> node_id | hostname | port | status | lb_weight | role<br>
> ---------+------------+------+--------+-----------+---------<br>
> 0 | pgserver01 | 3432 | 2 | 0.500000 | primary<br>
> 1 | pgserver02 | 3432 | 3 | 0.500000 | standby<br>
> (2 rows)<br>
> 3- pgpool.conf - attached<br>
> <br>
> Kind Regards,<br>
> <br>
> <br>
> On Tue, Dec 31, 2019 at 3:18 AM Tatsuo Ishii <<a href="mailto:ishii@sraoss.co.jp" target="_blank">ishii@sraoss.co.jp</a>> wrote:<br>
> <br>
>> Looks strange. It seems every time client_idle_limit is hit, failover<br>
>> happens, or vice versa. I need more info. Can you share:<br>
>><br>
>> - exact Pgpool-II version<br>
>> - output from "show pool_nodes"<br>
>> - pgpool.conf<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>
>> > Dear all<br>
>> > i have setup two nodes of postgres 9.4 with streaming replication and<br>
>> they<br>
>> > work fine as below command:<br>
>> ><br>
>> > $repmgr -f repmgr/repmgr.conf cluster show<br>
>> > Role | Connection String<br>
>> > * master | host=10.10.0.2 (pgserver01) port=3432 user=repmgr<br>
>> dbname=repmgr<br>
>> > standby | host=10.10.0.3(pgserver02) port=3432 user=repmgr<br>
>> dbname=repmgr<br>
>> ><br>
>> > and sometimes the slave being deatatched from pgpool while its running<br>
>> and<br>
>> > accepting data from master node but from pgadmin its beeing deattached<br>
>> and<br>
>> > the error below appears in pgpool logs :<br>
>> ><br>
>> > any one have an idea<br>
>> ><br>
>> ><br>
>> > ERROR: pid 1770: health check failed. 1 th host pgserver02 at port 3432<br>
>> is<br>
>> > down<br>
>> > ec 30 12:57:26 dataserver01 pgpool[1770]: 2019-12-30 12:57:26 LOG: pid<br>
>> > 40056: pool_process_query: child connection forced to terminate due to<br>
>> > client_idle_limit (180) reached<br>
>> > Dec 30 12:57:27 dataserver01 pgpool[1770]: 2019-12-30 12:57:27 LOG: pid<br>
>> > 9877: connect_inet_domain_socket: select() timed out. retrying...<br>
>> > Dec 30 12:57:27 dataserver01 pgpool[1770]: 2019-12-30 12:57:27 LOG: pid<br>
>> > 1770: connect_inet_domain_socket: select() interrupted<br>
>> > Dec 30 12:57:27 dataserver01 pgpool[1770]: 2019-12-30 12:57:27 ERROR: pid<br>
>> > 1770: make_persistent_db_connection: connection to pgserver02(3432)<br>
>> failed<br>
>> > Dec 30 12:57:27 dataserver01 pgpool[1770]: 2019-12-30 12:57:27 ERROR: pid<br>
>> > 1770: health check failed. 1 th host pgserver02 at port 3432 is down<br>
>> > Dec 30 12:57:27 dataserver01 pgpool[1770]: 2019-12-30 12:57:27 LOG: pid<br>
>> > 40604: connect_inet_domain_socket: select() timed out. retrying...<br>
>> > Dec 30 12:57:28 dataserver01 pgpool[1770]: 2019-12-30 12:57:28 LOG: pid<br>
>> > 40743: pool_process_query: child connection forced to terminate due to<br>
>> > client_idle_limit (180) reached<br>
>> > Dec 30 12:57:28 dataserver01 pgpool[1770]: 2019-12-30 12:57:28 LOG: pid<br>
>> > 43528: pool_process_query: child connection forced to terminate due to<br>
>> > client_idle_limit (180) reached<br>
>> > Dec 30 12:57:29 dataserver01 pgpool[1770]: 2019-12-30 12:57:29 LOG: pid<br>
>> > 42497: pool_process_query: child connection forced to terminate due to<br>
>> > client_idle_limit (180) reached<br>
>> > Dec 30 12:57:30 dataserver01 pgpool[1770]: 2019-12-30 12:57:30 LOG: pid<br>
>> > 42306: pool_process_query: child connection forced to terminate due to<br>
>> > client_idle_limit (180) reached<br>
>> > Dec 30 12:57:37 dataserver01 pgpool[1770]: 2019-12-30 12:57:37 LOG: pid<br>
>> > 9877: connect_inet_domain_socket: select() timed out. retrying...<br>
>> > Dec 30 12:57:37 dataserver01 pgpool[1770]: 2019-12-30 12:57:37 LOG: pid<br>
>> > 40604: connect_inet_domain_socket: select() timed out. retrying...<br>
>> > Dec 30 12:57:38 dataserver01 pgpool[1770]: 2019-12-30 12:57:38 LOG: pid<br>
>> > 44622: pool_process_query: child connection forced to terminate due to<br>
>> > client_idle_limit (180) reached<br>
>> > Dec 30 12:57:39 dataserver01 pgpool[1770]: 2019-12-30 12:57:39 LOG: pid<br>
>> > 42245: pool_process_query: child connection forced to terminate due to<br>
>> > client_idle_limi<br>
>><br>
</blockquote></div>