[ClusterLabs] Monitoring action of Pacemaker resources fail because of high load on the nodes

Klaus Wenninger kwenning at redhat.com
Tue Apr 26 05:58:04 UTC 2016


On 04/26/2016 06:04 AM, Ken Gaillot wrote:
> On 04/25/2016 10:23 AM, Dmitri Maziuk wrote:
>> On 2016-04-24 16:20, Ken Gaillot wrote:
>>
>>> Correct, you would need to customize the RA.
>> Well, you wouldn't because your custom RA will be overwritten by the
>> next RPM update.
> Correct again :)
>
> I should have mentioned that the convention is to copy the script to a
> different name before editing it. The recommended approach is to create
> a new provider for your organization. For example, copy the RA to a new
> directory /usr/lib/ocf/resource.d/local, so it would be used in
> pacemaker as ocf:local:mysql. You can use anything in place of "local".
>
But what you are attempting doesn't sound entirely proprietary.
So once you have something that looks like it might be useful
for others as well let the community participate and free yourself
from having to always take care of your private copy ;-)
>> Dimitri
>>
>>
>>
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org





More information about the Users mailing list