On Fri, 2024-01-26 at 13:55 +0100, lejeczek via Users wrote:
> Hi guys.
>
> Is it possible to trigger some... action - I'm thinking specifically
> at shutdown/start.
> If not within the cluster then - if you do that - perhaps outside.
> I would like to create/remove constraints, when cluster
On Mon, Jan 29, 2024 at 5:22 PM Ken Gaillot wrote:
> On Fri, 2024-01-26 at 13:55 +0100, lejeczek via Users wrote:
> > Hi guys.
> >
> > Is it possible to trigger some... action - I'm thinking specifically
> > at shutdown/start.
> > If not within the cluster then - if you do that - perhaps
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.
When both nodes are powered off and I power them on, they do not start
pacemaker at
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.
>
>
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
Thank you, Ken.
I changed my configuration management system to put an initial cib.xml into
/var/lib/pacemaker/cib/, which sets all the property values I was setting via
pcs commands, including dc-deadtime. I removed those "pcs property set"
commands from the ones that are run at startup
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
On Mon, 2024-01-29 at 22:48 +, Faaland, Olaf P. wrote:
> Thank you, Ken.
>
> I changed my configuration management system to put an initial
> cib.xml into /var/lib/pacemaker/cib/, which sets all the property
> values I was setting via pcs commands, including dc-deadtime. I
> removed those
>> However, now it seems to wait that amount of time before it elects a
>> DC, even when quorum is acquired earlier. In my log snippet below,
>> with dc-deadtime 300s,
>
> The dc-deadtime is not waiting for quorum, but for another DC to show
> up. If all nodes show up, it can proceed, but
