View a markdown version of this page

Reduced downtime Conductor Live upgrade - AWS Elemental Conductor Live

Reduced downtime Conductor Live upgrade

The process outlined in this section uses worker redundancy to limit the upgrade downtime. This process applies when the following are true:

  • The worker nodes are in a redundancy group.

  • You are upgrading the worker nodes and the AWS Elemental Conductor Live node or nodes to the same major version. For example, 2.25.5 and 3.25.5.

  • The cluster is in a working state. If any node is in a degraded state (not responding or not accepting jobs), the upgrade on that node won't work.

If these conditions don't apply, see Standard Conductor Live upgrade.

Note

In this procedure, we show how to upgrade from version 3.23.5 to version 3.25.5 (for Conductor Live ) and from version 2.23.5 to version 2.25.5(for worker nodes). Modify your commands to specify the version that you are upgrading to.

To check the type of redundancy of your deployment

  1. On the web interface for the primary Conductor Live node, access Conductor Live > Redundancy.

  2. Look in the Redundancy Group task bar:

    • If you find any groups labeled as Live, your cluster is using worker redundancy and you can perform the reduced downtime upgrade.

    • If you find any groups labeled as Conductor Live, your cluster is using Conductor Live redundancy (high availability).

The following procedure shows the comprehensive reduced downtime upgrade process. This process is valid whether or not you have Conductor Live redundancy. It will guide you to your next step based on your circumstances through the steps provided.

Topics