[pgpool-hackers: 583] Re: [pgpool-committers: 2070] pgpool: Change connect() timeout longer (10 seconds) for flaky network.
ishii at postgresql.org
Sat Jul 12 21:51:08 JST 2014
I have changed connect() timeout (actually it's the timeout of right
after select()). This is necessary for flaky network such as AWS.
This is for the known problem described in:
The fix is back patched to 3.3 and 3.2. 3.3 or before does not need
the patch since they do not use non-block connect().
> Change connect() timeout longer (10 seconds) for flaky network.
> Change connect() timeout in connect_inet_domain_socket_by_port() from
> 1 second to 10 seconds for flaky network such as AWS. This should help
> reducing frequent failover. Pgpool-II 3.4 will have switch to control
> the timeout value, rather than fixed value. However our policy does
> not allow to add new feature like that. So I decided to just tweak the
> fixed value.
> Modified Files
> pool_connection_pool.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> pgpool-committers mailing list
> pgpool-committers at pgpool.net
More information about the pgpool-hackers