Ken Gaillot wrote:
> Pacemaker's upstream master branch has a new feature that will be part
> of the eventual 1.1.15 release.
[snipped]
> This new feature makes updates of Pacemaker Remote nodes more similar to
> that of cluster nodes -- simply stop cluster services (in this case
> pacemaker_rem
Pacemaker's upstream master branch has a new feature that will be part
of the eventual 1.1.15 release.
Since version 1.1.10, Pacemaker has supported Pacemaker Remote nodes to
scale a cluster beyond the limits of a full cluster stack (and to manage
resources inside a VM that is itself managed by th
On 02/19/2016 09:50 AM, Richard Stevenson wrote:
> Hi,
>
> I'm having trouble updating pacemaker on a small 3 node cluster. All nodes
> are running Centos 7, and I'm upgrading via a simple `yum upgrade`.
> Whenever I attempt to do this the node is fenced when yum attempts to clean
> up the old pac
Hi,
I'm having trouble updating pacemaker on a small 3 node cluster. All nodes
are running Centos 7, and I'm upgrading via a simple `yum upgrade`.
Whenever I attempt to do this the node is fenced when yum attempts to clean
up the old pacemaker package - restarted by STONITH in this case.
Updating
Jan, thank you for the answer. I still have few questions.
Also, FYI, this happened on a cluster with just one node.
The cluster is designed to be a two-node cluster, with possibility to work
even with only one node.
and if corosync was not scheduled for more than token timeout "Process
paus
Michal Koutný napsal(a):
On 02/18/2016 10:40 AM, Christine Caulfield wrote:
I definitely remember looking into this, or something very like it, ages
ago. I can't find anything in the commit logs for either corosync or
cman that looks relevant though. If you're seeing it on recent builds
then it'
