>>> Ken Gaillot schrieb am 19.12.2022 um 22:07 in
>>> Nachricht
<68e568cdcd675f8e4de8b01cd3ed27e2eb4ed28c.ca...@redhat.com>:
...
> If simultaneous monitors is somehow causing the problem, you should be
> able to work around it by using different intervals for different
> monitors.
I disagree:
>>> Thomas CAS schrieb am 19.12.2022 um 10:48 in Nachricht
:
> Hello Clusterlabs,
>
> I would like to report a bug on Pacemaker with the "IPaddr2" resource:
>
> OS: Debian 10
> Kernel: Linux wd‑websqlng01 4.19.0‑18‑amd64 #1 SMP Debian 4.19.208‑1
(2021‑09‑29)
> x86_64 GNU/Linux
> Pacemaker
>>> Andrei Borzenkov schrieb am 19.12.2022 um 14:17 in
Nachricht
:
> On Mon, Dec 19, 2022 at 4:01 PM Antony Stone
> wrote:
>>
>> On Monday 19 December 2022 at 13:55:45, Andrei Borzenkov wrote:
>>
>> > On Mon, Dec 19, 2022 at 3:44 PM Antony Stone
>> >
>> > wrote:
>> > > So, do I simply create
On Mon, 2022-12-19 at 09:48 +, Thomas CAS wrote:
> Hello Clusterlabs,
>
> I would like to report a bug on Pacemaker with the "IPaddr2"
> resource:
>
> OS: Debian 10
> Kernel: Linux wd-websqlng01 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1
> (2021-09-29) x86_64 GNU/Linux
> Pacemaker version:
Hi,
Some OS vendors, including Red Hat and SUSE, provide training for their
own ClusterLabs-based offerings. At least B1 Systems (
https://www.b1-systems.de/schulung/) and Guru Labs (
https://www.gurulabs.com/linux-training/courses/) offer courses as
well.
On Wed, 2022-12-14 at 02:06 +,
On Mon, 2022-12-19 at 16:17 +0300, Andrei Borzenkov wrote:
> On Mon, Dec 19, 2022 at 4:01 PM Antony Stone
> wrote:
> > On Monday 19 December 2022 at 13:55:45, Andrei Borzenkov wrote:
> >
> > > On Mon, Dec 19, 2022 at 3:44 PM Antony Stone
> > >
> > > wrote:
> > > > So, do I simply create one
Hello Clusterlabs,
I would like to report a bug on Pacemaker with the "IPaddr2" resource:
OS: Debian 10
Kernel: Linux wd-websqlng01 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1
(2021-09-29) x86_64 GNU/Linux
Pacemaker version: 2.0.1-5+deb10u2
You will find the configuration of our cluster with 2
On Mon, Dec 19, 2022 at 4:01 PM Antony Stone
wrote:
>
> On Monday 19 December 2022 at 13:55:45, Andrei Borzenkov wrote:
>
> > On Mon, Dec 19, 2022 at 3:44 PM Antony Stone
> >
> > wrote:
> > > So, do I simply create one stonith resource for each server, and rely on
> > > some other random server
On Monday 19 December 2022 at 13:55:45, Andrei Borzenkov wrote:
> On Mon, Dec 19, 2022 at 3:44 PM Antony Stone
>
> wrote:
> > So, do I simply create one stonith resource for each server, and rely on
> > some other random server to invoke it when needed?
>
> Yes, this is the most simple
On Mon, Dec 19, 2022 at 3:44 PM Antony Stone
wrote:
>
> So, do I simply create one stonith resource for each server, and rely on some
> other random server to invoke it when needed?
>
Yes, this is the most simple approach. You need to restrict this
stonith resource to only one cluster node (set
Hi.
I have a 7-node corosync / pacemaker cluster which is working nicely as a
proof-of-concept.
Three machines are in data centre 1, three are in data centre 2, and one
machine is in data centre 3.
I'm using location contraints to run one set of resources on any of the
machines in DC1,
11 matches
Mail list logo
