>>> Lars Marowsky-Bree <lmb@suse.com> schrieb am 25.01.2014 um 18:07 in
Nachricht
<20140125170730.GB9317@suse.de>:
> On 2014-01-24T10:52:56, Tom Parker <tparker@cbnco.com> wrote:
>
>> Thanks Kristoffer.
>>
>> How is tuning done for lrm now?
>
> What do you want to tune?
>
> The LRM_MAX_CHILDREN setting is still (okay: again ;-), that was broken
> in one update) honored as before. Or you can use the "node-action-limit"
> property in the CIB to achieve the same, without setting environment
> variables; in case you don't like the automatic attempt at load
> dampening that pacemaker deploys.
Talking on "node-action-limit": I think I read in the syslog (not the best way
to document changes) that the "migration-limit" parameter is obsoleted by
"node-action-limit" in lastest SLES. Ist that correct?
If so I think that's a poor decision, because a Xen live migration for a
multi-GB-RAM-VM is a heavy weight process, while other actions are most likely
much more lightweight, and VM migration probably does not benefit for parallel
execution or multiple CPUs as it's very much I/O-heavy (not to say net-heavy).
crmd[16709]: warning: cluster_option: Using deprecated name 'migration-limit'
for cluster option 'node-action-limit'
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
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Nachricht
<20140125170730.GB9317@suse.de>:
> On 2014-01-24T10:52:56, Tom Parker <tparker@cbnco.com> wrote:
>
>> Thanks Kristoffer.
>>
>> How is tuning done for lrm now?
>
> What do you want to tune?
>
> The LRM_MAX_CHILDREN setting is still (okay: again ;-), that was broken
> in one update) honored as before. Or you can use the "node-action-limit"
> property in the CIB to achieve the same, without setting environment
> variables; in case you don't like the automatic attempt at load
> dampening that pacemaker deploys.
Talking on "node-action-limit": I think I read in the syslog (not the best way
to document changes) that the "migration-limit" parameter is obsoleted by
"node-action-limit" in lastest SLES. Ist that correct?
If so I think that's a poor decision, because a Xen live migration for a
multi-GB-RAM-VM is a heavy weight process, while other actions are most likely
much more lightweight, and VM migration probably does not benefit for parallel
execution or multiple CPUs as it's very much I/O-heavy (not to say net-heavy).
crmd[16709]: warning: cluster_option: Using deprecated name 'migration-limit'
for cluster option 'node-action-limit'
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
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems