t; *From: *Users on behalf of Faaland, Olaf
> P. via Users
> *Date: *Monday, January 29, 2024 at 7:46 PM
> *To: *Ken Gaillot , Cluster Labs - All topics
> related to open-source clustering welcomed
> *Cc: *Faaland, Olaf P.
> *Subject: *Re: [ClusterLabs] controlling cluster b
DC election happens quickly once both nodes are up.
That makes sense
> Thanks,
> Chris
>
> From: Users on behalf of Faaland,
> Olaf P. via Users
> Date: Monday, January 29, 2024 at 7:46 PM
> To: Ken Gaillot , Cluster Labs - All topics
> related to open-source clustering
C election
happens quickly once both nodes are up.
Thanks,
Chris
From: Users on behalf of Faaland, Olaf P. via
Users
Date: Monday, January 29, 2024 at 7:46 PM
To: Ken Gaillot , Cluster Labs - All topics related to
open-source clustering welcomed
Cc: Faaland, Olaf P.
Subject: Re: [Cluster
3:49 PM
To: Faaland, Olaf P.; Cluster Labs - All topics related to open-source
clustering welcomed
Subject: Re: [ClusterLabs] controlling cluster behavior on startup
On Mon, 2024-01-29 at 22:48 +, Faaland, Olaf P. wrote:
> Thank you, Ken.
>
> I changed my configuration management system t
On Mon, 2024-01-29 at 14:35 -0800, Reid Wahl wrote:
>
>
> On Monday, January 29, 2024, Ken Gaillot wrote:
> > On Mon, 2024-01-29 at 18:05 +, Faaland, Olaf P. via Users
> wrote:
> >> Hi,
> >>
> >> I have configured clusters of node pairs, so each cluster has 2
> >> nodes. The cluster
t;gopher11"/>
> name="cluster-recheck-interval" value="60"/>
> name="start-failure-is-fatal" value="false"/>
>
>
>
>
>
>
>
>
>
>
&g
en Gaillot
Sent: Monday, January 29, 2024 10:51 AM
To: Cluster Labs - All topics related to open-source clustering welcomed
Cc: Faaland, Olaf P.
Subject: Re: [ClusterLabs] controlling cluster behavior on startup
On Mon, 2024-01-29 at 18:05 +, Faaland, Olaf P. via Users wrote:
> Hi,
&g
On Monday, January 29, 2024, Ken Gaillot wrote:
> On Mon, 2024-01-29 at 18:05 +, Faaland, Olaf P. via Users wrote:
>> Hi,
>>
>> I have configured clusters of node pairs, so each cluster has 2
>> nodes. The cluster members are statically defined in corosync.conf
>> before corosync or
On Mon, 2024-01-29 at 18:05 +, Faaland, Olaf P. via Users wrote:
> Hi,
>
> I have configured clusters of node pairs, so each cluster has 2
> nodes. The cluster members are statically defined in corosync.conf
> before corosync or pacemaker is started, and quorum {two_node: 1} is
> set.
>
>
