On 12/03/20 08:22 +0100, Ulrich Windl wrote:
> Sorry for top-posting, but if you have NTP-synced your nodes,
> CLOCK_MONOTONIC will not have much advantage over CLOCK_REALTIME
> as the clocks will be rather the same,
I guess you mean they will be rather the same amongst the nodes
relative to each
On Wed, 2020-03-11 at 20:01 +0200, Roman Hershkovich wrote:
> But colocation of dbprobe won't pull trigger of webserver ? Or
> because that it is below in order - it will just restart services ?
I'm not sure what you mean. Resource failures don't cause node fencing
unless you explicitly ask for
On Wed, 2020-03-11 at 17:24 -0400, Marc Smith wrote:
> Hi,
>
> I'm using Pacemaker 1.1.20 (yes, I know, a bit dated now). I noticed
I'd still consider that recent :)
> when I modify a resource parameter (eg, update the value), this
> causes
> the resource itself to restart. And that's fine, but
Hi all,
TL;DR if you've been having problems, they hopefully will get better
now
We have gotten some reports of users being automatically unsubscribed
from this list, or not getting all messages from the list.
The issue is that some mail servers have become more strict about what
mail they
Hi!
Sorry for top-posting, but if you have NTP-synced your nodes, CLOCK_MONOTONIC
will not have much advantage over CLOCK_REALTIME as the clocks will be rather
the same, and they won't "jump". IMHO the latter is the main reason for using
CLOCK_MONOTONIC (if the admin decides to adjust the
