[Pacemaker] [Problem] The "dampen" parameter of the attrd_updater command is ignored, and an attribute is updated.

[Andrew Beekhof]

On 28 May 2014, at 3:04 pm, renayama19661014 at ybb.ne.jp wrote:

> Hi Andrew,
> 
>>> I'd expect that block to hit this clause though:
>>> 
>>>      } else if(mainloop_timer_running(a->timer)) {
>>>         crm_info("Write out of '%s' delayed: timer is running", a->id);
>>>         return;
>> 
>> Which point of the source code does the suggested code mentioned above revise?
>> (Which line of the source code is it?)
> 
> Is it the next cord that you pointed?

right

> 
> void
> write_attribute(attribute_t *a)
> {
>    int updates = 0;
> (snip)
>    } else if(mainloop_timer_running(a->timer)) {
>        crm_info("Write out of '%s' delayed: timer is running", a->id);
>        return;
>    }
> (snip)
> 
> At the time of phenomenon of the problem, the timer does not yet block it by this processing because it does not start.

Thats the curious part
-------------- 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/20140528/45b34ed9/attachment-0004.sig>