Hi all,
I noticed something odd.
[root@an-a02n01 ~]# pcs cluster status
Cluster Status:
Cluster Summary:
* Stack: corosync
* Current DC: an-a02n01 (version 2.0.4-6.el8_3.2-2deceaa3ae) -
partition with quorum
* Last updated: Tue Apr 27 23:20:45 2021
* Last change: Tue Apr 27
On Mon, 26 Apr 2021 18:04:41 + (UTC)
Strahil Nikolov wrote:
> I prefer that the stack is auto enabled. Imagine that you got a DB that is
> replicated and primary DB node is fenced. You would like that node to join
> the cluster and if possible to sync with the new primary instead of staying
>>> Ken Gaillot schrieb am 26.04.2021 um 20:06 in
Nachricht
:
> On Mon, 2021-04-26 at 17:04 +, Moneta, Howard wrote:
>> Hello community. I have read that it is not recommended to set
>> Pacemaker and corosync to enabled/auto start on the nodes. Is this
>> how people have it configured? If a
>>> damiano giuliani schrieb am 26.04.2021 um
20:04
in Nachricht
:
> Personally i discourage the use of the auto restarts/rejoin, if something
> wrong happened, better investigate the causes and then enable the failed
> node again.
Well, actually I find it less stressing if the cluster is
>>> "Moneta, Howard" schrieb am 26.04.2021 um 19:04 in
Nachricht
> Hello community. I have read that it is not recommended to set Pacemaker and
> corosync to enabled/auto start on the nodes. Is this how people have it
I think it's basically about your sleep at night or at weekends:
If the
