Description of problem: Message logged in engine.log is a bit misleading, making it more difficult to create/modify effective policies. [org.ovirt.engine.core.bll.scheduling.policyunits.CpuAndMemoryBalancingPolicyUnit] (DefaultQuartzScheduler_Worker-15) [187ca1cf] All hosts are over-utilized, can't balance the cluster 'Default' using the secondary method It implies it won't run the secondary method because all hosts are over-utilized. That's not true when using OptimalForPowerSaving balacer (and perhaps some other cases too). Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: - OptimalForPowerSaving Balancer - MinFreeMemoryForUnderUtilized of X GB - MaxFreeMemoryForOverUtilized of Y GB 1. Concentrate all VMs in one host, let it go under Y of free scheduling memory 2. Let the other host have more free memory than X Actual results: "All hosts are over-utilized, can't balance the cluster 'Default' using the secondary method" Expected results: "All hosts are over-utilized or under-utilized, can't balance the cluster 'Default' using the secondary method" OR "All hosts have been filtered, can't balance the cluster 'Default' using the secondary method" Additional info: 'underUtilizedHosts' ends up empty in backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/scheduling/policyunits/CpuAndMemoryBalancingPolicyUnit.java:101 when using 'getSecondaryDestinations' from OptimalForPowerSaving defined in backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/scheduling/policyunits/PowerSavingBalancePolicyUnit.java:340. This happens because this implementation of 'getSecondaryDestinations' filters BOTH OverUtilized and UnderUtilized hosts, but the message we log says only OverUtilized. No big deal and just making the log string more generic would be satisfactory. Or use some return codes to give a more detailed log.
Is this going to 4.0? 1. It cannot be set to 4.0.4 - this is our RC cycle, or even post RHV 4.0 GA - we don't want that. 2. Patches are still in draft. What is the status of this bug?
(In reply to Yaniv Kaul from comment #1) > Is this going to 4.0? > 1. It cannot be set to 4.0.4 - this is our RC cycle, or even post RHV 4.0 GA > - we don't want that. > 2. Patches are still in draft. > > What is the status of this bug? 1.need to verify with Doron / Roy 2.The patch is pending on code review (both on master and 4.0)
Also the wording "Secondary method" is not helping.
verified on : Red Hat Virtualization Manager Version: 4.0.4-0.1.el7ev verification steps: 1. create new cluster policy with OptimalForPowerSaving LOAD Balancer and the following parameters: - MinFreeMemoryForUnderUtilized of X GB - MaxFreeMemoryForOverUtilized of Y GB 2. set this new cluster policy on the cluster 3. Concentrate all VMs in one host, let it go under Y of free scheduling memory 4. Let the other host have more free memory than X can see the right Warning log : 2016-09-05 14:55:40,422 WARN [org.ovirt.engine.core.bll.scheduling.policyunits.CpuAndMemoryBalancingPolicyUnit] (DefaultQuartzScheduler9) [422a7cba] All candidate hosts have been filtered, can't balance the cluster 'golden_env_mixed_1' using memory based approach