Requested redundancy is incompatible with existing redundancy in vRealize Operations Manager 6.x

Products

• VMware Aria Suite

Issue/Introduction

Symptoms:

• The vRealize Operations Manager cluster is stuck in a Waiting for Analytics state.
• In the analytics.log file on one or more nodes, you see the errors:
  
  ERROR [Analytics Main Thread ] com.vmware.vcops.controller.gemfire.GemfireCommunicator.connect - Cannot connect to gemfire. The reason is Requested redundancy 0 is incompatible with existing redundancy 1
  ERROR [Analytics Main Thread ] com.vmware.vcops.controller.gemfire.GemfireCommunicator.connect - Cannot connect to gemfire. The reason is Requested redundancy 1 is incompatible with existing redundancy 0

Environment

VMware vRealize Operations Manager 6.2.x
VMware vRealize Operations Manager 6.1.x
VMware vRealize Operations Manager 6.0.x

Cause

This issue occurs when one or more nodes has the Shard Redundancy level set incorrectly from the rest of the nodes in the cluster.

Resolution

To resolve this issue, the Shard Redundancy level should to be corrected on the node(s) with the correct value.

To correct the Shard Redundancy level:

1. Log in to the master node as root through console or SSH.
2. Stop all VMware vRealize Operations Manager services by running this command:
   
   service vmware-vcops stop
   
   
3. Open the /usr/lib/vmware-vcops/user/conf/gemfire.properties file using a text editor.
4. Change the line shardRedundancyLevelto 1 (enabled) or 0 (disabled), depending on the state of HA.
   
   Note: The state of HA can be verified in the VMware vRealize Operations Manager admin UI of any node.
   
   
5. Save and close the file.
6. Repeat steps 1 to 5 on all nodes in the vRealize Operations Manager cluster.
7. Start all VMware vRealize Operations Manager services at the same time on all the nodes by running this command.
   
   service vmware-vcops start

Note: Shard Redundancy refers to High Availability in vRealize Operations Manager. Valid states for the redundancy level are 1, HA enabled, or 0, HA disabled.