On Wed, 2018-07-04 at 10:10 +0530, Pankaj wrote:
> Hi,
>
> We have facing problem pacemaker when ntp time sync is done. When
> time jumps forwards, we have seen that fail-count timer would not
> expire as expected. There are other issues like pacemaker discarding
> old events.
>
> It seems pacemaker is not using monotonic clock.
> If this is the case, is it possible to use monotonic clock or if any
> patch is available or if there is any build option?
> If there is any workaround to handle this, please let me know.
Currently, no, pacemaker has no way to handle large time jumps. Jumps
forward aren't too bad, but jumps backward can cause significant
trouble.
> # pacemakerd --version
> Pacemaker 1.1.16
> Written by Andrew Beekhof
> # corosync -v
> Corosync Cluster Engine, version '2.4.2'
> Copyright (c) 2006-2009 Red Hat, Inc.
>
> Regards,
> Pankaj
--
Ken Gaillot
___
Users mailing list: Users@clusterlabs.org
https://lists.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
