Cluster initialization takes long time in vRealize Operatons Manager 6.x
search cancel

Cluster initialization takes long time in vRealize Operatons Manager 6.x

book

Article ID: 344395

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article provides steps to set date and time across vRealize Operations Manager nodes within a 30 second tolerance.

Symptoms:
  • The cluster takes a long time to initialize after bringing the cluster online.
  • The cluster takes a long time to initialize after expanding the cluster.


Environment

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

Cause

This issue occurs when the date and time across vRealize Operations Manager nodes is not matched within a 30 second tolerance.

Resolution

To resolve the issue, set the date and time on each vRealize Operations Manage node to be within 30 seconds tolerance of one another.
Note: Refer to the documentation of your Operating System for steps on changing the date and time.
On the vRealize Operations Manager appliance, follow the steps:
  1. Log in to the Master node using root credentials through SSH or Console.
  2. Set the date by running the command:

    date -s YYYY-MM-DD

    Note: Replace YYYY with the year, MM with the month, and DD with the day.

    For example: date -s 2016-11-07

  3. Set the time by running the command:

    date -s hh:mm:ss

    Note: Replace hh with the hours, mm with the minutes, and ss with the seconds based on a 24 hour clock.

    For example: date -s 12:05:30

  4. Repeat steps 2 and 3 on all vRealize Operations Manager nodes in the cluster.


Additional Information

vRealize Operatons Manager 6.x でクラスタの初期化に時間がかかる
在 vRealize Operatons Manager 6.x 中初始群集花费很长时间