[ClusterLabs] Antw: Problem with pacemaker resources when NTP sync is done

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Wed Jul 4 03:16:44 EDT 2018

 >>> Pankaj <pankaj386 at gmail.com> schrieb am 04.07.2018 um 06:40 in Nachricht
<CAO5O8CyVbhto10j4RKrJBu_jsKNCEcidhMK9dwds56piNSEcYg at mail.gmail.com>:
> 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.


I would investigate _why_ your clock jumps.

> 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?

IMHO POSIX' CLOCK_MONOTONIC is no solution, because you cannot compare those monotonic clock values between machines. However using timer_create(CLOCK_MONOTONIC, ...) might help for the problem if the problem is there.


> If there is any workaround to handle this, please let me know.
> #  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

More information about the Users mailing list