Performing a standard cluster migration on an AWS Elemental Conductor File cluster - AWS Elemental Conductor File

Performing a standard cluster migration on an AWS Elemental Conductor File cluster

This procedure describes how to take the nodes in a AWS Elemental Conductor File cluster from a version below 2.18 and migrate them to version 2.18 or higher. The nodes in the cluster might be the following:

  • A primary Conductor node and, optionally, a secondary Conductor node.

  • AWS Elemental Server nodes.

Important

We strongly recommend that you test the entire migration procedure in your lab. This strategy lets you test the migration process itself, and test the entire workflow on the new software.

In this procedure, we show how to upgrade the cluster from Conductor File version 2.17.5 (worker nodes version 2.17.5) to version 2.17.5). Modify the commands you enter to match your versions.

Important

You must upgrade all the nodes in the cluster to a 2.18 version. You can't, for example, set up the cluster so that Conductor File is running 2.17 and the workers (or some of the workers) are running 2.18.