Strahil,
I will try to get into the details on monday, when I have access to the cluster again.I guess the
Perfect, thanks
/var/log/cluster/corosync.log and /etc/corosync/corosync.conf are the
most interesting.
Yup, for now these are the most important.
So far, I have 6 node cluster with
On 3/13/21 12:55 AM, Strahil Nikolov wrote:
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
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
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
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
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 RH subsciption, so RH devs will provide more detailed output
on the issue.
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+).
Knet waits for enough pong replies for other nodes before it marks them
as
