[pgpool-general: 4203] Re: Heartbeat random fails between pgpool instances

[Thomas SIMON]

Hi Yugo,
thanks for your reply.

I'll check it out asap and will come back to you after that.

Thomas

Le 04/11/2015 08:04, Yugo Nagata a écrit :
> Hi,
>
> On Tue, 03 Nov 2015 11:09:14 +0100
> Thomas SIMON <tsimon at neteven.com> wrote:
>
> It think a heartbeat signal was broken and both pgpool came to regard
> another pgpool as down.
>
>> Parameters :
>>
>> db10:
>> delegate_IP = '172.25.1.5'
>> wd_lifecheck_method = 'heartbeat'
>> wd_interval = 10
>> wd_heartbeat_port = 9694
>> wd_heartbeat_keepalive = 20
>> wd_heartbeat_deadtime = 30
>> heartbeat_destination0 = 'db11.xxx.com'
>> heartbeat_destination_port0 = 9694
>> heartbeat_device0 = 'eth3'
> In this configuration, heartbeat signals are sent every 20 sec, and
> the deadtime  30 sec. So, if even one heartbeat signal isn't sent for
> some reason then it reaches deadtime. It is reccomended to specify
> more small value to wd_heartbeat_keepalive or raise wd_heartbeat_deadtime.
>
>>
>>
>> db11:
>> wd_lifecheck_method = 'heartbeat'
>> wd_interval = 10
>> wd_heartbeat_port = 9694
>> wd_heartbeat_keepalive = 20
>> wd_heartbeat_deadtime = 30
>> heartbeat_destination0 = 'db10.neteven.com'
>> heartbeat_destination_port0 = 9694
>> heartbeat_device0 = 'eth5'
>>
>>
>>
>> Does anyone has an idea ?
>>
>> Thanks
>>
>> -- 
>>
>> Thomas
>>
>> _______________________________________________
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
>> http://www.pgpool.net/mailman/listinfo/pgpool-general
>