BUT also either make warntime smaller or deadtime larger...
On 5/13/2011 7:48 PM, [email protected] wrote:
Thank you for your attention.
His recommendation and wait, if only to continue the logs I get
following warning if the services do not migrate to another server
just keep watching the logs warning.
> I typically make deadtime something like 3 times warntime. That way
> you'll get data before you get into trouble. When your heartbeats
> exceed warntime, you get information on how late it is. I would
> typically make deadtime AT LEAST twice the latest time you've ever seen
> with warntime.
>
> If the worst case you ever saw was this 60ms instead of 50ms, I'd look
> somewhere else for the problem. However, it is possible that you have a
> hardware trouble, or a kernel bug. Possible, but unlikely.
>
> More logs are always good when looking at a problem like this.
> hb_report will get you lots of logs and so on for the next time it
happens.
>
> On 05/13/2011 11:44 AM, [email protected] wrote:
>> Thanks for the help.
>>
>> I had a problem the 30 days that began with this post, and after two
>> days the heartbeat message that the accused had fallen server1 and
>> services migrated to server2
>> Now with this change to eth1 and eth2 for drbd and heartbeat to the
>> amendment of warntime deadtime 20 to 15 and do not know if this will
>> happen again.
>> Thanks
>>
>> > That's related to process dispatch time in the kernel. It might
be the
>> > case that this expectation is a bit aggressive (mea culpa).
>> >
>> > In the mean time, as long as those timings remain close to the
>> > expectations (60 vs 50ms) I'd ignore them.
>> >
>> > Those messages are meant to debug real-time problems - which you
don't
>> > appear to be having.
>> >
>> > -- Alan Robertson
>> > [email protected]
>> >
>> >
>> > On 05/12/2011 12:54 PM, [email protected] wrote:
>> >> Hello!
>> >> I'm using heartbeat version 3.0.3-2 on debian squeeze with dedicated
>> >> gigabit ethernet interface for the heartbeat.
>> >> But even this generates the following message:
>> >> WARN: Gmain_timeout_dispatch: Dispatch function for send local
status
>> >> took too long to execute: 60 ms (> 50 ms) (GSource: 0x101c350)
>> >> I'm using eth1 to eth2 and to Synchronize DRBD(eth1) HEARBEAT
(eth2).
>> >> I tried increasing the values deadtime = 20 and 15 warntime
>> >> Interface Gigabit Ethernet controller: Intel Corporation 82575GB
>> >> Serv.1 and the Ethernet controller: Broadcom Corporation
NetXtreme II
>> >> BCM5709 in Serv.2
>> >> Tested using two Broadcom for the heartbeat, also without success.
>> >>
>> >> Thanks
>> >
>> > --
>>
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
