[ClusterLabs] Antw: pacemaker doesn't correctly handle a resource after time/date change

Digimer lists at alteeve.ca
Fri Jul 24 12:59:01 EDT 2015

On 24/07/15 01:56 AM, Ulrich Windl wrote:
>>>> Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com> schrieb am 23.07.2015
> um 18:09 in Nachricht
> <CAEnTH0eKJV8udjp5GobJpp8yOVzRcT_XSuV7gn93topPALCh2g at mail.gmail.com>:
>> Hi,
>> If you do:
>>     # date --set="1990-01-01 01:00:00"
> Why would you do that in a running cluster?

>From a stability/HA perspective, you need to consider all (though
unlikely) things that might go wrong. Time suddenly changing (a little
or a lot) shouldn't break the cluster. So though it might seem silly on
the surface, if this is a reproducible problem, it should probably be

>> when only one node is present in the cluster and while the cluster is
>> working, and then stop a resource (any resource), the cluster fails the
>> resource once, shows it as Started, but the resource actually is still
>> stopped.
>> Is it the expected behavior in the cluster?
>> Is it prohibited to change time/date while the cluster is working?
>> The environment: two node cluster with just one node up; pacemaker 1.1.12.
>> Thank you,
>> Kostya
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?

More information about the Users mailing list