Hi Florian, ok I've checked the thread, so that means that on RHEL6 , if I have let's say 32 resources groups of 2 primitives on each node, I can set the LRMD_MAX_CHILDREN environment variable in /etc/sysconfig/pacemaker to 64 ? Is it acceptable for lrmd and Pacemaker ? Or will we face any side-effect ? Thanks Alain
De : Florian Haas <[email protected]> A : General Linux-HA mailing list <[email protected]> Date : 21/11/2011 12:58 Objet : Re: [Linux-HA] Antw: What about "start-delay" attribute status ? Envoyé par : [email protected] On 11/21/11 13:03, [email protected] wrote: > Hi, > yes that's exactly the purpose of my question (and exactly the same > problem of "big-monitoring-trains") : > if we can always use start-delay to ramdomize the first monitor operation > time on all the resources on a server, > but if it is really deprecated, that means that in the future this option > will no more > be managed by Pacemaker (perhaps it already is the case ... ?) , so in > this case > we must not use this option. > > Could someone give us a clear status on this option "start-delay" ? If your RA needs it, then the RA is most likely broken. :) For monitor operations allegedly piling up, please consider this: http://www.gossamer-threads.com/lists/linuxha/pacemaker/76152#76152 Hope this helps. Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
