[ClusterLabs] Antw: Re: Antw: Re: Antw: pacemaker doesn't correctly handle a resource after time/date change
konstantin.ponomarenko at gmail.com
Wed Jul 29 08:44:33 EDT 2015
So, is it considered as a bug in Pacemaker?
Buy the way, while the "failure-timeout" is set to 1 hour and with the
"cluster-recheck-interval" of 15 min, the resource is started by the
cluster sometime after 1 hour and 15 min time period.
On Mon, Jul 27, 2015 at 9:09 AM, Ulrich Windl <
Ulrich.Windl at rz.uni-regensburg.de> wrote:
> >>> Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com> schrieb am
> um 16:53 in Nachricht
> <CAEnTH0fPx9Zjj71gW92xordkOw1kk7kbT8xtO7M1En9w5MCyVw at mail.gmail.com>:
> > On Fri, Jul 24, 2015 at 1:21 PM, Ulrich Windl <
> > Ulrich.Windl at rz.uni-regensburg.de> wrote:
> >> 25 years backwards?
> > I've tried to set time back for:
> > 2 hours;
> > 10 min.
> > The result was the same as with:
> > # date --set="1990-01-01 01:00:00"
> > Setting time to 5 min back doesn't lead to that issue - the resource is
> > restarted.
> > There is no such problem with setting time forward.
> I'm afraid no programmer ever took provisions for time running backwards.
> It may be as simple as that. Recently thres has been even heavy discussion
> (elsewhere) about the bad effects of inserting a leap second, realizing
> that the POSIX interface has to means of detecting a leap second...
> > P.S.:The resource has it's monitor interval set to 30 sec.
> > Thank you,
> > Kostya
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users