Indeed, the cluster is quite sluggish when responding to the events, but
still acceptable for me - since the priority is to have it running with
many nodes. In my case the network is quite heavily used, but the shared
storage was limited. The settings, which worked for the 55 nodes I tested,
were
On 2016-09-02 10:09, Ken Gaillot wrote:
On 09/02/2016 08:14 AM, Dan Swartzendruber wrote:
So, I was testing my ZFS dual-head JBOD 2-node cluster. Manual
failovers worked just fine. I then went to try an acid-test by
logging
in to node A and doing 'systemctl stop network'. Sure enough,
On 09/02/2016 08:14 AM, Dan Swartzendruber wrote:
>
> So, I was testing my ZFS dual-head JBOD 2-node cluster. Manual
> failovers worked just fine. I then went to try an acid-test by logging
> in to node A and doing 'systemctl stop network'. Sure enough, pacemaker
> told the APC fencing agent
On 09/01/2016 09:39 AM, Scott Greenlese wrote:
> Andreas,
>
> You wrote:
>
> /"Would be good to see your full cluster configuration (corosync.conf
> and cib) - but first guess is: no fencing at all and what is your
> "no-quorum-policy" in Pacemaker?/
>
> /Regards,/
> /Andreas"/
>
> Thanks
It occurred to me folks reading this might not have any knowledge about
ZFS. Think of my setup as an mdraid pool with a filesystem mounted on
it, shared out via NFS. Same basic idea...
___
Users mailing list: Users@clusterlabs.org
So, I was testing my ZFS dual-head JBOD 2-node cluster. Manual
failovers worked just fine. I then went to try an acid-test by logging
in to node A and doing 'systemctl stop network'. Sure enough, pacemaker
told the APC fencing agent to power-cycle node A. The ZFS pool moved to
node B as
Kostiantyn Ponomarenko writes:
> Hi,
>
>>> If "scripts: no-quorum-policy=ignore" is becoming depreciated
> Are there any plans to get rid of this option?
> Am I missing something?
The above is talking about crmsh cluster configuration scripts, not core
Hello everyone!
Today I am releasing crmsh version 2.3.1. The only change this time is
to lower the Python version requirement from 2.7 to 2.6. This is so
that crmsh remains compatible with centOS 6, where there is no
standardized Python 2.7 version available. For users of other
distributions