[Pacemaker] resource monitor priority - timeout on high load

emmanuel segura emi2fast at gmail.com
Mon Oct 5 14:08:09 EDT 2015

If I remeber, there is a way to make real time pacemaker process, but
I don't know if this can help you, you need to tell us if your server
high load is system space or userspace.

2015-10-05 19:53 GMT+02:00 Radoslaw Garbacz
<radoslaw.garbacz at xtremedatainc.com>:
> Hi,
> I have a situation, when resource monitor operations timeout on system high
> load.
> One thing to do is to increase timeouts, but there can always be load, at
> which the timeout event would happen, and on the other hand too long
> timeouts would not be very useful, so I would like to increase the priority
> of monitoring processes (GNU Linux), but I do not want to be too broad.
> So my question is, which pacemaker process should I target to ensure timely
> monitoring operations, or maybe even there is a pacemaker configuration
> parameter, which would help in such a case.
> I know for sure, that agents finish they monitoring requests on time, and
> the timeout is due to high load. I have several agents, so I will provide
> just some details to illustrate the case:
> - timeout: ~60s
> - interval: ~60s
> - normal (low load) monitor request time: 0.2s
> - high load monitor request time: 8s - when pacemaker reports resource
> operation timeout
> Thanks,
> --
> Best Regards,
> Radoslaw Garbacz
> XtremeData Incorporation
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 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 Pacemaker mailing list