[Pacemaker] Time-based location constraint not working in HB 2.1.4?

[Andreas Kurz]

Andrew Beekhof wrote:
> 
> On Dec 12, 2008, at 10:32 AM, Andreas Kurz wrote:
> 
>> Andrew Beekhof wrote:
>>>
>>> On Dec 11, 2008, at 1:53 PM, Andreas Kurz wrote:
>>>
>>>> Andrew Beekhof wrote:
>>>>> Have you read the section on "Ensuring Time Based Rules Take Effect" ?
>>>>
>>>> Yes ... but in the "Configuration Explained" document for Pacemaker 0.6
>>>> this section is (nearly) empty.
>>>>
>>>> In the latest version for Pacemaker 1.0.1 I found the hint about the
>>>> "cluster-recheck-interval" ... but it has no effect on my config ...
>>>> too
>>>> old Pacemaker version? .. a "ptest metadata" gives no description for
>>>> this attribute.
>>>
>>> crmd metadata (its a crmd option)
>>
>> ahh ... good to know ;-)
>>
>>>
>>> try with underscores instead of the dashes
>>
>> hmm ... has no effect:
>>
>> # crm_attribute -G -n cluster_recheck_interval
>> name=cluster_recheck_interval value=3min
> 
> did you restart the node?  its only read once - at startup.
> otherwise it could be a bug in 2.1.4

huh ... no, I did not restart the node ... are all these crmd options
only read at startup? Is a restart of heartbeat on both nodes needed ...
or only on the current DC?

Anyway ... not a job before weekend ;-) I'll give it a try next week.

thx & Regards,
Andreas

> 
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at clusterlabs.org
> http://list.clusterlabs.org/mailman/listinfo/pacemaker
>