[ClusterLabs] Is STONITH resource location special?

Hi, Pacemaker Explained discusses in 13.3 the special treatment of STONITH resources. Now, I configured 6 fence_ipmilan instances in a cluster which runs on 4 nodes currently. No STONITH resource started on the node it can kill, even though I haven't configured location constraints yet. Is

Re: [ClusterLabs] Fencing questions.

On 19/10/15 06:53 AM, Arjun Pandey wrote: > Hi > > I am running a 2 node cluster with this config on centos 6.5/6.6 where It's important to keep both nodes on the same minor version, particularly in this case. Please either upgrade centos 6.5 to 6.6 or both to 6.7. > i have a multi-state

Re: [ClusterLabs] Coming in 1.1.14: remapping sequential reboots to all-off-then-all-on

On 10/19/2015 11:42 AM, Digimer wrote: > On 19/10/15 12:34 PM, Ken Gaillot wrote: >> Pacemaker supports fencing "topologies", allowing multiple fencing >> devices to be used (in conjunction or as fallbacks) when a node needs to >> be fenced. >> >> However, there is a catch when using something

[ClusterLabs] Coming in 1.1.14: remapping sequential reboots to all-off-then-all-on

Pacemaker supports fencing "topologies", allowing multiple fencing devices to be used (in conjunction or as fallbacks) when a node needs to be fenced. However, there is a catch when using something like redundant power supplies. If you put two power switches in the same topology level, and

[ClusterLabs] Automatic IPC buffer adjustment in Pacemaker 1.1.11?

Hi, The http://www.ultrabug.fr/tuning-pacemaker-for-large-clusters/ blog post states that "Pacemaker v1.1.11 should come with a feature which will allow the IPC layer to adjust the PCMK_ipc_buffer automagically". However, I failed to identify this in the ChangeLog. Did it really happen, can I

Re: [ClusterLabs] Corosync & pacemaker quit between boot and login

On Fri, Oct 16, 2015 at 06:25:29PM +0200, users-requ...@clusterlabs.org wrote: > From: Russell Martin > Subject: [ClusterLabs] Corosync & pacemaker quit between boot and login > > ... > Both corosync and pacemaker seem to start fine during boot (they both say > "[OK]")