Upgrading Cluster Nodes

Upgrading cluster nodes can be done while the Cluster Manager is running, and does not require that the Cluster Manager itself is also upgraded.

  1. Review the ATC Manager release notes.
    Review the release notes for the versions that were released since your current version. In particular, the Breaking Changes section highlights changes that may require you to adjust your workflow, configuration, or usage.
  2. Confirm that you have received the new cluster node image from Aspera.
    You can find the AMI ID in the ATC Manager release notes.
  3. Open the Cluster Configuration file.
    On the Clusters page of the Cluster Manager UI, click Action > Edit Cluster Configuration in the row for your cluster.
  4. Update the cluster node source image.
    Locate the setting "source_image" in the Cluster Configuration text box and update its value with the new node image ID that was provided to you by Aspera.
  5. Click Save Changes to start the upgrade.
    The change to "source_image" triggers Cluster Manager to launch replacement nodes for all existing cluster nodes and phase out old nodes.

    You can confirm that the nodes are being upgraded by watching their replacement and checking the version of Enterprise Server that each one is running. From the Clusters page of the Cluster Manager UI, click the number in the Nodes column to open the Monitor Nodes page. The Current Pool column shows the replacment status (REPLACEMENT IN PROGRESS for new nodes, and IDLE or RUNNING if the node is pending replacement or is replaced. Click each node to view the version of Enterprise Server and confirm it is the one associated with your upgrade.

    If the node is listed as DEGRADED after an upgrade and the NODE service is shown with an ERROR status, continue to the next step.

  6. If you are upgrading from a version of ATCM that predates 1.2.2, update the aspera.conf section with a required setting.
    On the Clusters page, click the cluster and go to the Transfer Configuration tab. Click Edit. Add the following line to the <server> section:
    This setting is required by Cluster Manager to use the Node API for querying the status of transfers. As of version 1.2.2, cluster templates include this setting.
  7. If you are upgrading from a version of ATCM that predates 1.2.3, update the database.
    Once all nodes are upgraded, log into one of the nodes (using SSH) and run the following command:
    # /opt/aspera/bin/asnodeadmin --db-update
    This command updates the Redis database that is used by the Node API to the latest format. To activate the database update, you must trigger a restart of asperanoded on the nodes. Go to the Transfer Configuration tab for the cluster and click Edit. Add a space after a setting (not within a tag) and save your changes.