[pgpool-general: 6061] Re: "health check timer expired" on local machine

[Bud Curly]

*> *So if we had health_check_hostname0, does it help you?

*This could be a workaround for my case but I believe this is a network
issue from my server provider. I don't really know about their network
structure, but the public ip address used is set at an higher level trough
NAT and it's not affected on the network interface of the server itself. *
With the command tracepath from the machine to its public IP, I found out
that it goes trough 8 node to resolve.

So in general the use of public IP instead of loopback is not good in terms
of performance for local services.

A setting that could interest me could be : recovery_hostname0,
recovery_hostname1, etc. as I need the public IP only for standby to
perform pgpool_recovery().

Thanks :)

*Tatsuo Ishii* ishii at sraoss.co.jp
<pgpool-general%40pgpool.net?Subject=Re:%20Re%3A%20%5Bpgpool-general%3A%206060%5D%20Re%3A%20pgpool-general%20Digest%2C%20Vol%2078%2C%20Issue%2019&In-Reply-To=%3C20180427.174736.1303932718741225970.t-ishii%40sraoss.co.jp%3E>
*Fri Apr 27 17:47:36 JST 2018*

>* Thanks for your support :)
*
You are welcome:-)

>>* Still I don't understand. Pgpool-II and PostgreSQL master are on thesame
*>* machine, that means you could set like "backend_hostname0 = "127.0.0.1".
*> >* Because I need the public address for pgpool_recovery() method to permit
*>* online recovery from remote nodes. And pgPool like health_check
*>* process use backend_hostname0
*>* to do so.
*
Oh that makes sense.

>* The setting health_check_hostname0 doesn't exist but trough, this is not a
*>* workaround.
*
So if we had health_check_hostname0, does it help you?

>* So according to the log, is the timeout error triggered by this
*>* "health_check_timeout = 6" or this "connect_timeout = 10000" ?
*
I believe "health_check_timeout = 6". connect system call waits up to
10 seconds but before it expires health_check_timeout comes.

>* I downed timeout to 2 seconds each and monitoring net paquets to find some
*>* details... Keep you in touch
*
Thanks.

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




2018-04-27 10:44 GMT+02:00 Bud Curly <psyckow.prod at gmail.com>:

> Thanks for your support :)
>
> > Still I don't understand. Pgpool-II and PostgreSQL master are on thesame
> machine, that means you could set like "backend_hostname0 = "127.0.0.1".
>
> Because I need the public address for pgpool_recovery() method to permit
> online recovery from remote nodes. And pgPool like health_check process
> use backend_hostname0 to do so.
>
> The setting health_check_hostname0 doesn't exist but trough, this is not a
> workaround.
>
> So according to the log, is the timeout error triggered by this
> "health_check_timeout = 6" or this "connect_timeout = 10000" ?
>
> I downed timeout to 2 seconds each and monitoring net paquets to find some
> details... Keep you in touch
>
>
> 2018-04-27 3:15 GMT+02:00 Tatsuo Ishii <ishii at sraoss.co.jp>:
>
>> > Pgpool-II health check process uses non-blocking socket for connecting
>> > to PostgreSQL. After issuing connect system call it waits for its
>> > completion using select system call with timeout: connect_timeout in
>> > pgpool.conf (in your case 10 seconds). On the other hand health_check
>> > timeout is 6 seconds. So after 6 seconds, an alarm interrupted the
>> > select system call and it returned with errno == EINTR, then the log
>> > emitted. Not sure why the connect system call did not respond for 6
>> > seconds.
>> >
>> > That's all what I know from the log.
>>
>> If you want to make research on this, packet dump is required.
>>
>> Best regards,
>> --
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>> Japanese:http://www.sraoss.co.jp
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20180427/c6e344e4/attachment-0001.html>