[Pacemaker] [Problem] lrmd detects monitor time-out by revision of the system time.

[Andrew Beekhof]

On 8 Sep 2014, at 12:46 pm, renayama19661014 at ybb.ne.jp wrote:

> Hi Andrew,
> 
> Thank you for comments.
> 
>>> I confirmed some problems, but seem to be caused by the fact that an event 
>> occurs somehow or other in g_main_loop of lrmd in the period when it is shorter 
>> than a monitor.
>> 
>> So if you create a trivial program with g_main_loop and a timer, and then change 
>> the system time, does the timer expire early?
> 
> Yes.

That sounds like a glib bug. Ideally we'd get it fixed there rather than work-around it in pacemaker.
Have you spoken to them at all?

> 
>  
>>> This problem does not seem to happen somehow or other in lrmd of PM1.0.
>> 
>> cluster-glue was probably using custom timeout code.
> 
> 
> I watched implementation of glue, too.
> The time-out handling of new lrmd seems to have to perform implementation similar to glue somehow or other.
> 
> 
> Best Regards,
> Hideo Yamauchi.
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140908/2845e09d/attachment-0004.sig>