Re: [ClusterLabs] Problem with pacemaker resources when NTP sync is done
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
Re: [ClusterLabs] crm --version shows "cam dev"
On Wed, 2018-07-04 at 17:52 +0200, Salvatore D'angelo wrote: > Hi, > > With crash 2.2.0 the command: > cam —version > works fine. I downloaded 3.0.1 and it shows: > crm dev > > I know this is not a big issue but I just wanted to verify I > installed the correct version of crash. > It's probably right, but can you describe in more detail from where you downloaded and how you installed it? Cheers, Kristoffer > ___ > 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 ___ 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
[ClusterLabs] crm --version shows "cam dev"
Hi, With crash 2.2.0 the command: cam —version works fine. I downloaded 3.0.1 and it shows: crm dev I know this is not a big issue but I just wanted to verify I installed the correct version of crash. ___ 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
[ClusterLabs] Antw: Problem with pacemaker resources when NTP sync is done
>>> Pankaj schrieb am 04.07.2018 um 06:40 in Nachricht : > 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
