>>> Lars Marowsky-Bree <[email protected]> schrieb am 10.06.2013 um 15:11 in Nachricht <[email protected]>: > On 2013-06-05T15:36:47, Ulrich Windl <[email protected]> wrote: > >> Also set placement-strategy="utilization" then. If you put >> "utilization big_thing=1" into each fat primitives, your server won't >> be overloaded, but groups aren't moved if only one primitive cannot be >> run (a bug IMHO). I'm unsure whether you can put utilizations at the >> group level. >> >> In my understanding the group should summarize all the individual >> primitives utilizations, but it does not. To complete the >> non-rationale, stickinesses are summarized for groups, not maximized >> (i.e.: taking the largest value). > > This is no longer true. Utilization of resources within a group is now > summed up, and that will also lead to the group being moved in the > former case.
Interesting: Since when is this effective? We had some resource groups where the "fattest" primitive was the last one. If resources were tight, everything started, except the last one, but the group was never moved to another node with ample resources available. (Last seen in SLES11 SP2) Regards, Ulrich > > > Regards, > Lars > > -- > Architect Storage/HA > SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, > HRB 21284 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > _______________________________________________ > 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
