Compare upgrades from 7.3.x or 7.4.x with upgrades from 7.5.x

This topic compares the steps involved in upgrades from 7.3.x or 7.4.x and upgrades from 7.5.x. For more details on the steps, see the following examples:

The following table summarizes the differences in the upgrade steps for both upgrade paths.

Steps Upgrades from 7.3.x or 7.4.x Upgrades from 7.5.x

Perform checks on the old installation

If you are using Apache Cassandra:

  • You must check that embedded Apache Cassandra is configured correctly in your old installation.

If you do not wish to use Apache Cassandra in your new installation:

  • You must check and remove any Cassandra-backed KPS collections in your old installation.

No Apache Cassandra checks are necessary on the old installation, as the external Cassandra configuration is retained when upgrading from 7.5.x.

Install 7.5.3 using the Custom installation option

If you are using Apache Cassandra:

  • To install Apache Cassandra locally on a node alongside API Gateway, select to install the Cassandra component.
  • To install Apache Cassandra remotely, do not select to install the Cassandra component.
  • In either case you must configure an Apache Cassandra database cluster in the new installation.

If you do not wish to use Apache Cassandra in your new installation:

  • Do not select to install the Cassandra component.

Do not select to install the Apache Cassandra component, as the external Cassandra configuration is retained when upgrading from 7.5.x.

If you are using Apache Cassandra:

  • You can upgrade your version of Cassandra from 2.2.5 to 2.2.8 after you upgrade API Gateway. API Gateway 7.5.3 supports version 2.2.8 (recommended) and version 2.2.5 (for backwards compatibility).

Perform checks on the new installation

If you are using Apache Cassandra:

  • You must configure an Apache Cassandra database cluster in the new installation.

You do not need to configure an Apache Cassandra database cluster in the new installation, as the external Cassandra configuration is retained when upgrading from 7.5.x.

If you are using Apache Cassandra:

  • You must open the port 9042 on your firewall to enable API Gateway to communicate with Apache Cassandra, or you can configure API Gateway to use a different port after the upgrade.

Run export and upgrade commands

If you are using Apache Cassandra:

  • You must specify the host name or IP address of the new external Cassandra cluster to the upgrade command using the --cass_host option.

If you are not using Apache Cassandra:

  • You must run the upgrade command with the --no_cassandra option.

If you are using Apache Cassandra:

  • In a multi-node upgrade, you must specify the host name or IP address of the existing external Cassandra cluster to the upgrade command using the --cass_host option.
  • In a single-node upgrade, you do not need to specify the host name or IP address of the existing external Cassandra database cluster to the upgrade command, as the external Cassandra configuration is retained when upgrading from 7.5.x.

If you are not using Apache Cassandra:

  • In a multi-node upgrade, you must run the upgrade command with the --no_cassandra option.
  • In a single-node upgrade, you do not need to run the upgrade command with the --no_cassandra option.

 

Run apply command

If you are using Apache Cassandra:

  • You must update cassandra.yaml with the host name or IP address of the new external Cassandra cluster.
  • You must start Cassandra before you run apply.

If you are using Apache Cassandra:

  • You do not need to update the cassandra.yaml file or start Cassandra, as Cassandra should already be running.

Related Links