[pgpool-general: 6054] Re: "health check timer expired" on local machine
ishii at sraoss.co.jp
Fri Apr 27 07:55:47 JST 2018
> Hi and thanks for your work.
> I use pgpool2 3.7.2 (latest git) with 2 backend as master-slave mode with
> native stream replication.
> I think I have an issue concerning the health check process.
> Since two days now I had two "health check timer expired" that appears
> yersterday around 9 am and today around 8 pm.
> The weird thing is... Pgpool and the backend in question are on the same
> machine. This backend is the master. Here is the log :
> Despite the fact that these are on the same machine, I use public IP for
> the backend0 and not 127.0.0.1, because of failover process that required
> this ip.
Can you elaborate more? As far as I know, there's no reason for the
heath check process to not accept 127.0.0.1.
> Do you think this could be a problem from network conditions on the server
> itself or an actual issue ?
Yes. Was PostgreSQL busy at that time?
SRA OSS, Inc. Japan
More information about the pgpool-general