>>> Pankaj <pankaj...@gmail.com> schrieb am 04.07.2018 um 06:40 in Nachricht <cao5o8cyvbhto10j4rkrjbu_jskncecidhmk9dwds56pinse...@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.
Hi! 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. Regards, Ulrich > 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 _______________________________________________ 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
