Quorum doesn't prevent split-brains,
stonith (fencing) does.
https://www.alteeve.com/w/The_2-Node_Myth
There is no way to use quorum-only to avoid a potential
split-brain. You might be able to make it less likely with enough
effort, but never
Hello All,
Split-brain situation occurs due to there is a drop in quorum which leads to
Spilt-brain situation and status information is not exchanged between both two
nodes of the cluster.
This can be avoided if quorum communicates between both the nodes.
I have checked the code. In My opinion
On 2017-11-14 05:23 PM, Ken Gaillot wrote:
> ClusterLabs announces the release of version 1.1.18 of the Pacemaker
> cluster resource manager. The source code is available at:
>
> https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.18
>
> This is expected to be the last actively
ClusterLabs announces the release of version 1.1.18 of the Pacemaker
cluster resource manager. The source code is available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.18
This is expected to be the last actively developed release in the 1.1
line. Development will now
Systemd version 227 introduced a new unit file option, TasksMax, to
limit the number of processes that a service can spawn at one time.
Depending on the version, the default is either 512 or 4,915.
It is conceivable in a large cluster that Pacemaker could exceed this
limit, so we are now
On 13/11/17 17:06, Jan Friesse wrote:
Jonathan,
I've finished (I hope) proper fix for problem you've seen, so can you
please try to test
https://github.com/corosync/corosync/pull/280
Thanks,
Honza
Hi Honza,
Thanks very much for putting this fix together.
I'm happy to confirm that I
ClusterLabs is happy to announce resource-agents v4.1.0 rc1.
Source code is available at:
https://github.com/ClusterLabs/resource-agents/releases/tag/v4.1.0rc1
The most significant enhancements in this release are:
- new resource agents:
- aws-vpc-route53
- LVM-activate
- minio
-
