Thanks for the clarifications guys!
Il giorno mar 27 apr 2021 alle ore 18:24 Jehan-Guillaume de Rorthais <
j...@dalibo.com> ha scritto:
> 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
> >
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
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 down.
One such example is the SAP HANA DB. Imagine that the current
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 computer restarts unexpectedly,
> is it better to manually
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.
failovers shouldnt occour frequently, only if something went really bad: as
far i know, pacemaker and PAF doesnt support any kind of
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 computer restarts unexpectedly, is it better to manually
investigate first or allow the node to come back online and rejoin the