Workload Placement - Optimization Potential - You're hitting your maximum optimization potential

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• You are trying to determine why this error is seen for cross cluster migrations when in Aria Operations > Capacity > Workload Placement :
  
  "You're hitting your maximum optimization potential"
  
  
• The cluster status still shows "not optimized"
• In the  /storage/log/vcops/log/placement-UUID.log you may see the entries:
  
  
  YYYY-MM-DDTHH:MM:SS,800+0000 ERROR [WLP Executor worker thread 3] com.vmware.vcops.analytics.wlpautomation.WLPAutomationDistScheduler.run - Failed to generate re-balance plan for [C]DC= ########-####-####-####-############: [The stress of the selected container cannot be reduced.]

YYYY-MM-DDTHH:MM:SS,965+0000 INFO [Function Execution Processor40159] com.vmware.vcops.wlp.helper.vsphere.VSpherePlacementDataConversionUtil.convertReportToRebalanceActions - Failed move attempt: null

Environment

Aria Operations 8.18.x

Cause

The clusters in the Datacenters are all stressed, for example, CPU utilization may be maxed out , so there is nowhere for the workload to move without causing even more workload stress elsewhere.

• There is no other cluster in the Datacenter where the VMs can fit
• VMs under the stressed cluster are participating in DRS rules. (The VMs that are part of DRS rule will not be relocated to other clusters)
• VMs are not compatible with other clusters

Resolution

There is no immediate resolution for this issue. The cause is environmental and will require reducing overall cluster stress in the Datacenters or adding more capacity.

Additional Information

Configuring Workload Optimization - Prerequisites