HCL Commerce Version 9.1.15.0 or later

Migrating to a dual nodegroup configuration

Existing environments can be migrated to a split Auth and Live configuration.

About this task

To minimize down time, a new Elasticsearch cluster can be installed on a separate name space while the original installation remains active. Indices on the new environment can be created by first migrating the authoring environment to the new Elasticsearch cluster and reindexing, or by exporting and importing the indices on the new cluster using the snapshot feature. Once the new cluster is up and running with current indices, the live environment can be switched to the new cluster.

Practice these steps in a pre-production environment and do the migration during an off-peak period.

Procedure

  1. Complete a new Elasticsearch cluster installation with dedicated Auth and Live node groups.
  2. Update the Elasticsearch endpoint configuration in Vault. Configure live (svt/qa/live/elasticSearchHost) to the existing cluster, and authoring (svt/qa/elasticSearchHost) to the new cluster. See Connecting to Elasticsearch.
  3. Configure NiFi to enable the dual node group configuration. See Configuring NiFi.
  4. Restart all the authoring pods. At this point, live should continue running against the original Elasticsearch cluster, while authoring is connected to the new dual node configuration
  5. Run auth.reindex to populate the indices, and then run push-to-live.
  6. Validate the environment to confirm that the indices were created on the correct Elasticsearch nodes. See Validating the environment.
  7. Configure live (svt/qa/live/elasticSearchHost) in Vault to the new Elasticsearch cluster
  8. Restart the QueryApp servers, and use the cache manager application to clear all caches. The QueryApp servers should now be using the new dual node group configuration.
  9. The original Elasticsearch environment be can shutdown at this point.