Configure Nodes in Secondary Data Center for Omnissa Access

After you create nodes in the secondary data center by using the OVA file exported from the primary data center, configure the nodes for OpenSearch replication.

Prerequisites

Manually set the cluster.initial\_master\_nodes value to the FQDN for the secondary cluster before you configure the nodes in the secondary data center. See Configure OpenSearch for Nodes in Secondary Data Center for Omnissa Access.

Procedure

Follow these steps for each node in the secondary data center.

1. Add the load balancer FQDN of the primary data center cluster to the /usr/local/horizon/conf/runtime-config.properties file of each node in the secondary data center cluster.

   1. Access the /usr/local/horizon/conf/runtime-config.properties file for editing.

   vi /usr/local/horizon/conf/runtime-config.properties

   vi /usr/local/horizon/conf/runtime-config.properties

   2. Change the following line in the file:

      analytics.replication.peers=https://LB\_FQDN\_of\_second\_cluster

   to

    `analytics.replication.peers=https://LB\_FQDN\_of\_primary\_cluster`
   

2. Restart the Omnissa Access service on all the nodes.

   service horizon-workspace restart

3. Verify that the cluster is set up correctly by running the following command on all the nodes in the cluster.

   curl 'http://localhost:9200/_cluster/health?pretty'

   The command, which verifies OpenSearch health, should return a result similar to the following.

   {
     "cluster_name" : "horizon",
     "status" : "green",
     "timed_out" : false,
     "number_of_nodes" : 3,
     "number_of_data_nodes" : 3,
     "discovered_master" : true,
     "active_primary_shards" : 90,
     "active_shards" : 180,
     "relocating_shards" : 0,
     "initializing_shards" : 0,
     "unassigned_shards" : 0,
     "delayed_unassigned_shards" : 0,
     "number_of_pending_tasks" : 0,
     "number_of_in_flight_fetch" : 0,
     "task_max_waiting_in_queue_millis" : 0,
     "active_shards_percent_as_number" : 100.0
   }