[pgpool-general: 4268] Re: Pgpool - connection hangs in DISCARD ALL

[Tatsuo Ishii]

> Hello Tatsuo,
> 
> Thnx. Integrated this patch, will give you feedback. Hasn't the patch
> been included in the 3.4.x release series, yet?
>
> Only in 3.3.x series?

Not in 3.4.x (x <= 3).

> Because it is a patch from 2014 I guess.
> http://www.pgpool.net/mantisbt/view.php?id=107
> 
> According to the release notes 3.3.4 has it already fixed:
> http://www.pgpool.net/docs/pgpool-II-3.4.0/NEWS.txt

Yeah, it should have been included in 3.4 series earlier.

> Would be great if you could release a stable 3.4.4 with this major
> issue fixed,

Yes, we are going to release 3.4.4 in coming January.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

> Thnx.
> 
> Ciao,
> Gerhard
> 
> On 28.12.2015 06:47, Tatsuo Ishii wrote:
>> Looks it has been fixed in this commit:
>>
>> http://git.postgresql.org/gitweb/?p=pgpool2.git;a=commit;h=04a288318951869587f74e808b243115dfcb2652
>>
>> Best regards,
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese:http://www.sraoss.co.jp
>>
>>> Hello,
>>>
>>> Looks like the issue with hanging connections has not been solved in
>>> all cases, backend hangind in DISCARD ALL, TCP connection is still
>>> alive, but pgpool doesn't know the connection anymore.
>>>
>>> Version: pgpool: 3.4.3
>>> PostgreSQL: 9.4.5
>>>
>>> Relevant pgpool config:
>>> listen_addresses = '*'
>>> child_life_time = 10
>>> child_max_connections = 10
>>> connection_life_time = 2
>>>
>>> # One connection to the clients, but backend connection still alive
>>> netstat -pan | grep pgpool | grep -i ESTABLISHED
>>> tcp 0 0 127.0.0.1:50176 127.0.0.1:5432 ESTABLISHED 32119/pgpool: hei
>>> tcp 0 0 127.0.0.1:50180 127.0.0.1:5432 ESTABLISHED 32119/pgpool: hei
>>> tcp 0 0 127.0.0.1:52268 127.0.0.1:5432 ESTABLISHED 9967/pgpool: wait f
>>> tcp 0 0 192.168.20.104:9999 192.168.20.113:42760 ESTABLISHED
>>> 32119/pgpool: hei
>>>
>>> pcp_proc_info for all returned:
>>> Database     : ab3
>>> Username     : nag
>>> Start time   : 2015-12-27 15:48:38
>>> Creation time: 2015-12-27 15:49:16
>>> Major        : 3
>>> Minor        : 0
>>> Counter      : 1
>>> Backend PID  : 32141
>>> Connected    : 0
>>> Database     : hei
>>> Username     : hei
>>> Start time   : 2015-12-27 15:48:38
>>> Creation time: 2015-12-27 15:49:16
>>> Major        : 3
>>> Minor        : 0
>>> Counter      : 1
>>> Backend PID  : 32143
>>> Connected    : 1
>>>
>>> # Tuned tcp stack:
>>> net.ipv4.tcp_keepalive_intvl=10
>>> net.ipv4.tcp_keepalive_probes=3
>>> net.ipv4.tcp_retries2=3
>>>
>>> Looks like that this bug in release 3.3.3 should have been fixed in
>>> 3.4. But I guess there are some corner cases still available.
>>> http://www.pgpool.net/docs/pgpool-II-3.4.0/NEWS.txt
>>>
>>> Had it only once yet, connection was terminated after some minutes
>>> automatically.
>>>
>>> Any ideas?
>>>
>>> Thnx.
>>>
>>> Ciao,
>>> Gerhard
>>>
>>> _______________________________________________
>>> pgpool-general mailing list
>>> pgpool-general at pgpool.net
>>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>