[Docs][Admin] Add a note that MaxFreeMemoryForOverUtilized and MinFreeMemoryForUnderUtilized have to be both set when memory based scheduling is expected
Created attachment 1184593[details]
Memory based cluster auto balancing with imporant missing points highlight and imagesed
Description of problem:
Load balancing documentation is lacking some information regarding "CPU and Memory based cluster auto balancing".
In some scenarios, a user can choose only one threshold for memory balancing which will lead to unwanted results.
(see https://bugzilla.redhat.com/show_bug.cgi?id=1359767)
Additional points can be added to the documentation to clarify memory based load balancing.
The missing points and additional descriptive images are attached.
Version-Release number of selected component (if applicable):
4.0 upstream
How reproducible:
-
Steps to Reproduce:
See
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Technical_Reference/Load_Balancing_Policy.html
and in sections
5.4. Load Balancing Policy: Evenly_Distributed
5.5. Load Balancing Policy: Power_Saving
Actual results:
Some key points regarding memory based load balancing will be a part of the documentation
Expected results:
Add the needed information according to the attachment / wiki page.
1.highlighted points
2.images
3.other info that might seem important and missing (in lower priority)
Additional info:
-The most important missing items are marked in the attached document.
-wiki page can be found under
http://old.ovirt.org/Features/Sla/MemoryBasedBalancing
*please note - it is missing one important bullet
"Setting only one of the thresholds in memory based balancing (high or low) might lead to unexpected results."
(can be found in the attached document)
Comment 2Tahlia Richardson
2017-02-01 03:04:18 UTC
*** Bug 1376289 has been marked as a duplicate of this bug. ***