I will try to get into the details on monday, when I have access to the cluster
again.I guess the /var/log/cluster/corosync.log and /etc/corosync/corosync.conf
are the most interesting.
So far, I have 6 node cluster with separate VLANs for HANA replication, prod
and backup.Initially, I used pcs
Hi Sathish,
Sorry, I don't know how to get ruby 2.2.0 for RHEL 7.
The types of support have been explained by Ken. It has already been
said that pcs-0.10 is not supported on RHEL 7.
I would recommend to either downgrade to pacemaker 1.x and pcs-0.9, as
suggested by Ken, or upgrade your
Strahil,
Interesting...
Yet, this doesn't explain why token of 3 causes the nodes to never assemble
a cluster (waiting for half an hour, using wait_for_all=1) , while setting it
to 29000 works like a charm.
Definitively.
Could you please provide a bit more info about your setup
Got you!
Already create an issue in https://github.com/ClusterLabs/crmsh/issues/777 to
trace
Thank you!
Regards,
xin
From: Users on behalf of Ulrich Windl
Sent: Friday, March 12, 2021 4:41 PM
To: users@clusterlabs.org
Subject: [ClusterLabs] Antw: Re: Antw:
>>> Xin Liang schrieb am 12.03.2021 um 02:54 in Nachricht
> Hi Ulrich,
>
> Allow me to make this case simple:
> primitive d1 Dummy
> primitive d2 Dummy
> clone c1 d1
> clone c2 d2
> colocation col inf: c1 c2
> order ord inf: c2 ( c1 )
> Is above configuration similar with yours?
> Then after
Ulrich,
Jan Friesse schrieb am 11.03.2021 um 18:12 in Nachricht
:
Strahil,
Hello all,
I'm building a test cluster on RHEL8.2 and I have noticed that the cluster
fails to assemble ( nodes stay inquorate as if the network is not working) if
I set the token at 3 or more (30s+).
Hi!
I
>>> Jan Friesse schrieb am 11.03.2021 um 18:12 in
>>> Nachricht
:
> Strahil,
>> Hello all,
>> I'm building a test cluster on RHEL8.2 and I have noticed that the cluster
> fails to assemble ( nodes stay inquorate as if the network is not working) if
> I set the token at 3 or more (30s+).
On Thu, 11 Mar 2021 17:51:15 + (UTC)
Strahil Nikolov wrote:
> Interesting...
> Yet, this doesn't explain why token of 3 causes the nodes to never
> assemble a cluster (waiting for half an hour, using wait_for_all=1) , while
> setting it to 29000 works like a charm.
>
> Thankfully we got
On 3/11/21 7:03 PM, Strahil Nikolov wrote:
What about creating a custom fencing agent that does what you need and always
reporting that it failed ?
Using fencing topology and a custom fencing script as the first stonith device
(that always fails) , you will be able to execute some commands (or
