On Tue, 2022-03-08 at 17:20 +0100, Jehan-Guillaume de Rorthais wrote:
> Hi,
>
> Sorry, your mail was really hard to read on my side, but I think I
> understood
> and try to answer bellow.
>
> On Tue, 8 Mar 2022 11:45:30 +
> lejeczek via Users wrote:
>
> > On 08/03/2022 10:21,
On Tue, 8 Mar 2022 17:44:36 +
lejeczek via Users wrote:
> On 08/03/2022 16:20, Jehan-Guillaume de Rorthais wrote:
> > Removing the node attributes with the resource might be legit from the
> > Pacemaker point of view, but I'm not sure how they can track the dependency
> > (ping Ken?).
> >
>
On 08/03/2022 16:20, Jehan-Guillaume de Rorthais wrote:
Removing the node attributes with the resource might be legit from the
Pacemaker point of view, but I'm not sure how they can track the dependency
(ping Ken?).
PAF has no way to know the ressource is being deleted and can not remove its
Hi,
Sorry, your mail was really hard to read on my side, but I think I understood
and try to answer bellow.
On Tue, 8 Mar 2022 11:45:30 +
lejeczek via Users wrote:
> On 08/03/2022 10:21, Jehan-Guillaume de Rorthais wrote:
> >> op start timeout=60s \ op stop timeout=60s \ op promote
On Tue, 2022-03-08 at 10:24 +0200, Viet Nguyen wrote:
> Hi,
>
> May I know is there any API like REST or SOAP or some kind of Java
> libraries to interact with Pacemaker?
>
> I have a Java application and I would like to use that to monitor
> Pacemaker. Like viewing the resource statuses; and
On Tue, 8 Mar 2022 12:28:06 +
CHAMPAGNE Julie wrote:
> I didn't know the arguments order was so important. I should have read the
> doc at first! Thank you so much!!
You're welcome.
> Oh and just a last question, is there a way to prefer node1 as master for the
> resource pgsqld? I
Hi!
You may getting bored, but since the last message we had at least two more
kernel crashes, one on a machine with latest updates (firmware and SLES), and
the vendor diagnostics found no hardware problem.
The latest kdump (20 minutes ago) was:
---
[259832.062351] BTRFS info (device dm-0):
Wow !! It seems to work now!
I didn't know the arguments order was so important. I should have read the doc
at first! Thank you so much!!
Oh and just a last question, is there a way to prefer node1 as master for the
resource pgsqld? I probably need to define a score on it?
Thanks
Hello,
I've created the ressource pgsqld as follow (don't think the cluster creation
command is necessary):
pcs resource create pgsqld ocf:heartbeat:pgsqlms promotable \
PGDATA=/var/lib/postgresql/13/main \
bindir=/usr/lib/postgresql/13/bin \
start_opts="-c
Hi,
May I know is there any API like REST or SOAP or some kind of Java
libraries to interact with Pacemaker?
I have a Java application and I would like to use that to monitor
Pacemaker. Like viewing the resource statuses; and managing resources and
nodes like move resources or stop a node from
On 08/03/2022 10:21, Jehan-Guillaume de Rorthais wrote:
op start timeout=60s \ op stop timeout=60s \ op promote timeout=30s >> \ op demote timeout=120s \ op monitor interval=15s
timeout=10s >> role="Master" meta master-max=1 \ op monitor
interval=16s >> timeout=10s role="Slave" \ op notify
Hi,
On Tue, 8 Mar 2022 08:00:22 +
CHAMPAGNE Julie wrote:
> I've created the ressource pgsqld as follow (don't think the cluster creation
> command is necessary):
>
> pcs resource create pgsqld ocf:heartbeat:pgsqlms promotable \
The problem is here. The argument order given to pcs is
12 matches
Mail list logo
