[pgpool-hackers: 2280] Inifinite retrying to connect to backend

Tatsuo Ishii ishii at sraoss.co.jp
Tue Apr 25 10:30:40 JST 2017


Currently connect_with_timeout() performs infinite retry to connect to
backend if "retry" parameter of the function is true. This happens
when a client connects to Pgpool-II and there's no connection cache
for the request.

2017-04-25 09:54:50: pid 9379: LOG:  trying connecting to PostgreSQL server on "133.137.175.105:11003" by INET socket
2017-04-25 09:54:50: pid 9379: DETAIL:  timed out. retrying...
2017-04-25 09:54:50: pid 9379: LOCATION:  pool_connection_pool.c:623
2017-04-25 09:55:00: pid 9379: LOG:  trying connecting to PostgreSQL server on "133.137.175.105:11003" by INET socket
2017-04-25 09:55:00: pid 9379: DETAIL:  timed out. retrying...
2017-04-25 09:55:00: pid 9379: LOCATION:  pool_connection_pool.c:623
2017-04-25 09:55:10: pid 9379: LOG:  trying connecting to PostgreSQL server on "133.137.175.105:11003" by INET socket
:
:

This continues until health check detects the unavailability of the
backend. Note that if health check is disabled, it continues
forever. Maybe we should have separate configuration parameter from
health check to prevent the infinite retrying?

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


More information about the pgpool-hackers mailing list