Source code for the first release candidate for Pacemaker version 1.1.17
is now available at:
https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.17-rc1
The most significant enhancements in this release are:
* A new "bundle" resource type simplifies launching resources inside
On 05/05/2017 07:49 AM, Jan Wrona wrote:
> On 5.5.2017 08:15, Ulrich Windl wrote:
> Jan Wrona schrieb am 04.05.2017 um 16:41 in
> Nachricht
>> :
>>> I hope I'll be able to explain the problem clearly and correctly.
>>>
>>>
On 05/05/2017 12:37 AM, jitendra.jaga...@dell.com wrote:
>
>
> Hello All,
>
>
>
> Sorry for resurrecting old thread.
>
>
>
> I am also observing “High CPU load detected" messages in the logs
>
>
>
> In this email chain, I see everyone is suggesting to change
> "load-threshold"
On 04/28/2017 02:22 PM, Radoslaw Garbacz wrote:
> Hi,
>
> I have a question regarding pacemaker daemon shutdown
> procedure/configuration.
>
> In my case, when a remote node is lost pacemaker needs exactly 10minutes
> to shutdown, during which there is nothing logged.
> So my questions:
> 1.
If you look in the logs when the node comes back, there should be some
"pengine:" messages noting that the restarts will be done, and then a
"saving inputs in " message. If you can attach that file (both
with and without the constraint changes would be ideal), I'll take a
look at it.
On
On 05/08/2017 11:13 AM, Lentes, Bernd wrote:
> Hi,
>
> playing around with my cluster i always have a shell with crm_mon running
> because it provides me a lot of useful and current information concerning
> cluster, nodes, resources ...
> Normally i have a "crm_mon -nrfRAL" running.
> I'd like
Hi,
playing around with my cluster i always have a shell with crm_mon running
because it provides me a lot of useful and current information concerning
cluster, nodes, resources ...
Normally i have a "crm_mon -nrfRAL" running.
I'd like to have that output as a web page too.
So i tried the