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

[Kostiantyn Ponomarenko]

>>  I still fail to see the use case for setting the time backwards while
the cluster is up and running.
Essentially the issue can appear if NTP server is not reachable at the boot
time before the cluster is started (automatically) and a node for some
reason has a wrong time (say, 1 hour forward).
So, then, after NTP becomes reachable, the bug appears.

Thank you,
Kostya

On Mon, Aug 10, 2015 at 9:13 AM, Ulrich Windl <
Ulrich.Windl at rz.uni-regensburg.de> wrote:

> >>> Kostiantyn Ponomarenko <konstantin.ponomarenko at gmail.com> schrieb am
> 07.08.2015
> um 16:43 in Nachricht
> <CAEnTH0do6W8_eXTEVpUS6ehoBke7LiKtpPRAqpyARK7fwOu7dA at mail.gmail.com>:
> > Hi Andrew,
> >
> > So the issue is:
> >
> > Having one node up and running, set time on the node backward to, say, 15
> > min (generally more than 10 min), then do "stop" for a resource.
> > That leads to the next - the cluster fails the resource once, then shows
> it
> > as "started", but the resource actually remains "stopped".
>
> I guess it's due to chronology saying the resource had been stopped 15
> minutes before it was started. I still fail to see the use case for setting
> the time backwards while the cluster is up and running. Every cluster I
> know has the requirement of synchronized time. Synchronized time, in turn,
> implies that the time doesn't go backwards.
>
> Some databases use sequence numbers instead of time stamps, but It
> wouldn't surprise me if there were some US patent on that ;-)
>
> >
> > Do you need more input from me on the issue?
> >
> > Thank you,
> > Kostya
> >
> > On Wed, Aug 5, 2015 at 3:01 AM, Andrew Beekhof <andrew at beekhof.net>
> wrote:
> >
> >>
> >> > On 4 Aug 2015, at 7:31 pm, Kostiantyn Ponomarenko <
> >> konstantin.ponomarenko at gmail.com> wrote:
> >> >
> >> >
> >> > On Tue, Aug 4, 2015 at 3:57 AM, Andrew Beekhof <andrew at beekhof.net>
> >> wrote:
> >> > Github might be another.
> >> >
> >> > I am not able to open an issue/bug here
> >> https://github.com/ClusterLabs/pacemaker
> >>
> >> Oh, for pacemaker bugs see http://clusterlabs.org/help.html
> >> Can someone clearly state what the issue is?  The thread was quite
> >> fractured and hard to follow.
> >>
> >> >
> >> > 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
> >>
> >>
> >> _______________________________________________
> >> 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
> >>
>
>
>
>
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20150810/16b348c4/attachment-0002.html>