Search the VMware Knowledge Base (KB)
View by Article ID

Custom Datacenter or Datacenter Rebalance Recommendation Action fails in vRealize Operations Manager 6.x (2149865)

  • 0 Ratings

Symptoms

  • You receive the alert Datacenter may require rebalance or Custom Datacenter may require rebalance with the recommendation Rebalance the container to spread the workload more evenly.

  • Clicking Run Action results in an error similar to:

    The balance of the select container cannot be improved.

    Some moves were not eligible for the following reasons:
    4 virtual machines excluded since they failed compatibility checks for migration.


  • In the /storage/vcops/log/placement-uuid.log file, you see entries similar to:

    <YYYY-MM-DD>T<TIME>,373 DEBUG [ServerConnection on port 10000 Thread 1039] com.vmware.vcops.placement.manager.impl.FitAlgorithm.hasAccessToAllOrigSecondaryTargets - Cannot find original secondary target 60afa669-ff75-49ab-b9d6-75fac21523eb of source standalone-009c3676e-esx.3-vm.1 in destination secondary targets.
    <YYYY-MM-DD>T<TIME>,373 DEBUG [ServerConnection on port 10000 Thread 1039] com.vmware.vcops.placement.manager.impl.FitAlgorithm.canSupportLoadOnSharedSecondary - Provider cls55_1 is not connected to all original secondary providers of consumer standalone-009c3676e-esx.3-vm.1. Do not consider this provider.
    <YYYY-MM-DD>T<TIME>,373 DEBUG [ServerConnection on port 10000 Thread 1039] com.vmware.vcops.placement.manager.impl.FitAlgorithm.findTargetInTree - Not preferred candidate, skip target=cls55_2, source=standalone-009c3676e-esx.3-vm.1
    <YYYY-MM-DD>T<TIME>,374 TRACE [ServerConnection on port 10000 Thread 1039] com.vmware.vcops.placement.policy.impl.PlacementPolicyManagerImpl.getBadgeThreshold - getBadgeThreshold: Determining effective thresholdValue: Before: thresholdValue=80.0; useWorkload=true; minHeadroom=0.0
    <YYYY-MM-DD>T<TIME>,374 TRACE [ServerConnection on port 10000 Thread 1039] com.vmware.vcops.placement.policy.impl.PlacementPolicyManagerImpl.getBadgeThreshold - getBadgeThreshold: Determined effective thresholdValue: After: thresholdValue=80.0; useWorkload=true; minHeadroom=0.0
    <YYYY-MM-DD>T<TIME>,374 DEBUG [ServerConnection on port 10000 Thread 1039] com.vmware.vcops.placement.manager.impl.PlacementImpactCalculator.canSupportLoad - diskspace|demand workload of target cls55_1 is too high. Cannot fit more consumers. Workload = 84.0, threshold = 80.0

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue can occur if the Disk Space|Demand|Workload (%) metric has already breached or a rebalance would breach either the policy-defined Workload non-green threshold or the policy-defined Cluster Headroom buffer threshold. This is usually symptomatic of an environment that is "constrained" on Disk Space and hence limiting the possible moves despite the compute-focused alert.

Resolution

This is an expected behavior in vRealize Operations Manager 6.x.

To resolve this issue, in addition to ensuring that participating Compute Clusters and Datastore Clusters for rebalance are compatible, ensure that the environment has sufficient Disk Space to facilitate the Storage vMotion of VMDKs between Datastore Clusters to alleviate Compute imbalance through Compute vMotion.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: