Versions Compared

Old Version 9

changes.mady.by.user Kyle Miller

Saved on

compared with

New Version Current

changes.mady.by.user Bala Harish A(AC)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The Content Gateway software components are packaged as RPMs in the Swarm distribution bundles downloaded from the Downloads section on the DataCore Support Portal. Download the bundles for both Swarm 11 and Swarm 12 to verify all versions needed to step through a migration from an unsupported version of Elasticsearch are available.

Info

Elasticsearch

migration

Migration

Gateway 6 and higher cannot work with Elasticsearch 2.3.3, so be ready to switch over to the new search index before upgrading Gateway. Perform a rolling upgrade to the new Elasticsearch, taking advantage of the fact that each Gateway does not switch to the new Elasticsearch cluster until it is rebooted if more than one Gateway exists.

Work with DataCore Support to plan well and avoid down-timedowntime. See  See How to Upgrade Swarm, Upgrading from Unsupported Elasticsearch.

  1. Review the upgrade impacts and known issues for the release being upgraded

...

  1. .

...

  1. See Content Gateway Release Notes.

  2. Complete the upgrade of the Swarm Storage cluster.

  3. Complete the migration to Elasticsearch 6, so it is the primary search feed Gateway uses on restarting after upgrade.

...

  1. See Migrating from Older Elasticsearch.

  2. (Load balancer users only) In the load balancer, disable traffic for the specific Gateway being upgraded. Allow traffic to continue flowing to the other Gateways.

  3. Stop the Gateway service.

    Code Block
    languagebash
    systemctl stop cloudgateway

  4. Apply any operating system patches before upgrading the Gateway.

  5. Upgrade the RPMs for Gateway, Swarm UI, and Content UI:

    Code Block
    languagebash
    yum -y install caringo-gateway-VERSION.rpm
yum -y install caringo-storage-webui-VERSION.rpm
yum -y install caringo-gateway-webui-VERSION.rpm

  6. Reload the systemd control scripts:

    Code Block
    languagebash
    systemctl daemon-reload

  7. Fall back and retry if the upgrade failed:

    1. Revert the RPM back to Gateway 5.x.

    2. Restart the Gateway that failed the upgrade.

  8. Review and modify the gateway.cfg and the new logging.yaml configuration files in the /etc/caringo/cloudgateway directory.

...

  1. See Gateway Configuration.

    • gateway.

...

    • cfg In the [storage_cluster] section, update the indexerHosts value in to the new Elasticsearch server.

    • logging.yaml

...

    •   Edit the Syslog block and change the protocol to TCP if the server supports TCP and it is desired.

  2. The Gateway service does not automatically start after a system reboot, so re-enable the service if upgrading from version 5.2.1 or earlier.

...

  1. Code Block
    languagebash
    systemctl enable cloudgateway

  2. Start the Gateway service:

    Code Block
    languagebash
    systemctl start cloudgateway

  3. (Load balancer users only) Re-enable client traffic to the newly upgraded Gateway in the load balancer.

  4. Repeat the process for the remaining Gateways.

...