WORKS, but .... -- Re: [Pacemaker] Time-based location constraint not working in HB 2.1.4?

Andreas Kurz andreas.kurz at
Mon Dec 15 05:40:37 EST 2008

Andrew Beekhof wrote:
> On Dec 12, 2008, at 1:44 PM, Andreas Kurz wrote:
>> Andrew Beekhof wrote:
>>>>>> Is a restart of heartbeat on both nodes needed ...
>>>>>> or only on the current DC?
>>>>> Essentially everything.  Since restarting just the DC will result in
>>>>> another node being the DC.
>>>> Out of curiosity: why is the cluster_recheck_interval not enabled by
>>>> default with a value like 1min or 5min?
>>> Time-based rules aren't that common yet.
>> I understand ... but does it hurt to have it enabled? too much extra
>> load for the cluster?
> At the time it was thought so, but it's probably possible now.

I restarted the cluster with enabled cluster_recheck_interval and the
constraints work as expected, thanks for your help Andrew!

Now another question popped up ... how to deal with nodes running in
different time zones? At the moment the time-based rules are executed
according to the DCs time zone I suppose? There is no hidden feature to
specifiy a cluster-wide time zone to base time-based decisions on?


>> I expected the time-based rules to work
>> out-of-the-box without changing crmd options.
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at

More information about the Pacemaker mailing list