[pgpool-general: 3278] Re: Issues with pgpool 3.3.3 and failover
kargold100 at yahoo.com
Thu Nov 13 13:33:58 JST 2014
ok thanks a lot
From: Tatsuo Ishii <ishii at postgresql.org>
To: kargold100 at yahoo.com
Cc: pgpool-general at pgpool.net
Sent: Thursday, 13 November 2014 3:27 PM
Subject: Re: [pgpool-general: 3273] Issues with pgpool 3.3.3 and failover
Other thing I can think of is, upgrading RPM to
if you use CentOS6/RedHat6.
SRA OSS, Inc. Japan
> Thanks Tatsuo, is there anything else we can do instead of upgrading or changing the connect_inet_domain_socket_by_port().
> I am asking this as a temporary workaround till we upgrade to 3.3.4 Please advise
> From: Tatsuo Ishii <ishii at postgresql.org>
> To: kargold100 at yahoo.com
> Cc: pgpool-general at pgpool.net
> Sent: Thursday, 13 November 2014 3:18 PM
> Subject: Re: [pgpool-general: 3273] Issues with pgpool 3.3.3 and failover
> Probably this:
> Upgrading to 3.3.4 should fix the problem.
> Best regards,
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
>> Hi we have postgres 9.3.4 with pgpool 3.3 configured. we are facing the below errors and the pgpool goes out of sync though the streaming replication works fine:
>> :2014-11-10 02:47:25 ERROR: pid 26332: connect_inet_domain_socket: select() timed out
>> 2:2014-11-10 02:47:25 ERROR: pid 26332: make_persistent_db_connection: connection to node0(5432) failed
>> 3:2014-11-10 02:47:25 ERROR: pid 26332: health check failed. 0 th host node0 at port 5432 is down
>> the health_check_timeout is set to 15seconds and the system admin confirmed that there is network latency between the 2 nodes. there are no iptable rules set as well
>> Any idea why this issue is happening quiet frequenbtly and anything can be done to fix it permamently?
>> Thanks Karthick
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pgpool-general