Thanks Dejan, ok I understand, so we have to choose between a small value of LRMD_MAX_CHILDREN and on start, stop, or status of 64 resources it will take a while ... and a big value of LRMD_MAX_CHILDREN and then either the start, stop and at best, status will be achieved very quickly as they are parallelized or at worst the system will be "on knees" ... We'll give it a try ... as I have big computers ;-)
But my question is now : when you write : "Let me just add that operations which were supposed to start at the same time get spaced out." So if LRMD_MAX_CHILDREN=4, that means that if ask for start on 32 resources at the same time, Pacemaker will mange 4, delay the remaing 28, manage 4 again, etc. so it will be completed in 8 shots, right ? But what is the delay value between each shot ? Thanks Alain De : Dejan Muhamedagic <[email protected]> A : General Linux-HA mailing list <[email protected]> Date : 21/11/2011 13:45 Objet : Re: [Linux-HA] Antw: What about "start-delay" attribute status ? Envoyé par : [email protected] Hi, On Mon, Nov 21, 2011 at 01:42:15PM +0100, [email protected] wrote: > 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 ? The number of resources shouldn't be the main criteria for setting this parameter, but what can your nodes handle without being overloaded. So, 64 sounds sounds like you have some really big computers :) It also depends on the nature of the cluster resources. The default of 4 is rather conservative, perhaps nowadays 8 would be better. > Is it acceptable for lrmd and Pacemaker ? Or will we face any side-effect > ? LRMD_MAX_CHILDREN is the maximum number of resource operations allowed to run in parallel. Hope that that answers your question. Thanks, Dejan > 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 _______________________________________________ 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
