>>> Ken Gaillot schrieb am 10.03.2020 um 18:49 in
Nachricht
<3098_1583862581_5E67D335_3098_1270_1_91b728456223eea7c8a00516a91ede18ab094530.c
m...@redhat.com>:
> Hi all,
>
> This is not a big deal but I wanted to give a heads‑up for anyone who
> builds their own pacemaker packages.
>
> With
On Wed, 2020-03-11 at 02:27 +0200, Roman Hershkovich wrote:
> Yes.
> I have only 1 APP active at same time, and so I want this app to be
> restarted whenever DB changes. Another one is a "standby" APP, where
> all resources are shut.
> So i thought about adding some "service" script, which will
On Wed, 2020-03-11 at 08:20 +0100, Ulrich Windl wrote:
> > > > Ken Gaillot schrieb am 10.03.2020 um
> > > > 18:49 in
>
> Nachricht
> <3098_1583862581_5E67D335_3098_1270_1_91b728456223eea7c8a00516a91ede1
> 8ab094530.c
> m...@redhat.com>:
> > Hi all,
> >
> > This is not a big deal but I wanted to
On 06/03/20 13:22 +0200, Strahil Nikolov wrote:
On March 6, 2020 11:06:13 AM GMT+02:00, Oyvind Albrigtsen
wrote:
Hi Strahil,
It seems like it tries to set one based on the resource name, and from
a quick check it seems like it also did on RHEL 7.5.
Great, thank you very much for explanation. Regarding returning error - i
did not knew.
So, basically i can have a service, that will probe for master DB, in case
of its transfer - service will update /etc/hosts and return error, which
will be caught by pcs and it will restart whole dependent set
On Wed, 2020-03-11 at 16:08 +0200, Roman Hershkovich wrote:
> Great, thank you very much for explanation. Regarding returning error
> - i did not knew.
> So, basically i can have a service, that will probe for master DB, in
> case of its transfer - service will update /etc/hosts and return
>
But colocation of dbprobe won't pull trigger of webserver ? Or because that
it is below in order - it will just restart services ?
On Wed, Mar 11, 2020, 18:41 Ken Gaillot wrote:
> On Wed, 2020-03-11 at 16:08 +0200, Roman Hershkovich wrote:
> > Great, thank you very much for explanation.
On 11/03/20 09:04 -0500, Ken Gaillot wrote:
> On Wed, 2020-03-11 at 08:20 +0100, Ulrich Windl wrote:
>> You only have to take care not to compare CLOCK_MONOTONIC
>> timestamps between nodes or node restarts.
>
> Definitely :)
>
> They are used only to calculate action queue and run durations
Hi,
I'm using Pacemaker 1.1.20 (yes, I know, a bit dated now). I noticed
when I modify a resource parameter (eg, update the value), this causes
the resource itself to restart. And that's fine, but when this
resource is restarted, it doesn't appear to honor the full set of
constraints for that
