On Tue, 2019-03-19 at 21:49 +0100, Adam Budziński wrote:
> Not sure I got “or (due to two_node / wait_for_all in corosync.conf)
> waits until it can see the other node before doing anything” right. I
> mean according tohttps://access.redhat.com/solutions/1295713“Th
> e 'two_node' parameter sets
Not sure I got “or (due to two_node / wait_for_all in corosync.conf) waits
until it can see the other node before doing anything” right. I mean
according tohttps://access.redhat.com/solutions/1295713 “The 'two_node'
parameter sets the quorum to '1' and allows one node to remain quorate and
On Tue, 2019-03-19 at 15:55 +0100, Adam Budziński wrote:
> Hello Ken,
>
> Thank you.
>
> But if I have a two node cluster and a working fencing mechanism
> wouldn't it be enough to disable the corosync and pacemaker service
> on both nodes so when it fence they won't come up?
There's actually
Hello Ken,
Thank you.
But if I have a two node cluster and a working fencing mechanism wouldn't
it be enough to disable the corosync and pacemaker service on both nodes so
when it fence they won't come up?
Thank you
pon., 18.03.2019, 16:19 użytkownik Ken Gaillot
napisał:
> On Sat, 2019-03-16
