On 08/24/2017 04:24 PM, Ken Gaillot wrote:
> How could it know that, from a cold boot? It doesn't know if the other
> node is down, or up but unreachable. wait_for_all is how to keep that
> fencing from happening at every cluster start, but the trade-off is you
> can't cold-boot a partial cluster.
On Thu, 2017-08-24 at 15:53 -0500, Dimitri Maziuk wrote:
> On 08/24/2017 03:40 PM, Ken Gaillot wrote:
>
> > You could set wait_for_all to 0 in corosync.conf, then boot. The living
> > node should try to fence the other one, and proceed if fencing succeeds.
>
> Didn't I just read a thread that say
On 08/24/2017 03:40 PM, Ken Gaillot wrote:
> You could set wait_for_all to 0 in corosync.conf, then boot. The living
> node should try to fence the other one, and proceed if fencing succeeds.
Didn't I just read a thread that says it won't: the other node is
already down?
--
Dimitri Maziuk
Progr
On Thu, 2017-08-24 at 15:10 -0500, Dimitri Maziuk wrote:
> Hi everyone,
>
> I seem to remember seeing theis once before, but my google-fu is
> failing: I've a 2-node active-passive cluster, when I power up one node
> only, resources remain stopped. Is there a way to boot a cluster on one
> node on
PS. centos 7.latest w/ the current pcs/corosync/pacemaker rpms as
distributed by centos, resources are stonith:fence_scsi, IPaddr2, and ZFS.
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
Hi everyone,
I seem to remember seeing theis once before, but my google-fu is
failing: I've a 2-node active-passive cluster, when I power up one node
only, resources remain stopped. Is there a way to boot a cluster on one
node only?
-- Note that if I boot up the other node everything starts, and
