Upgrading Engines

Once you save a deployment, you cannot change the engine version. As a result, to upgrade to a later engine version, you must clone the original deployment and select the later engine version. The cloned deployment retains the configurations in the original deployment, with a few exceptions based on the selected engine version.

Important: Before you select a later engine version, be sure to review the appropriate engine release notes to understand the changes in the versions:
The steps that you use to upgrade an engine version depend on following deployment types:

Upgrading Engines for Self-Managed Deployments

Use the following steps to upgrade an engine version for a self-managed deployment.

Important: Before upgrading, verify that the machines that run the engine instances meet the installation requirements for the latest engine version. The minimum requirements for an engine can change with each version. See the minimum Data Collector requirements or the minimum Transformer requirements.
  1. Clone the self-managed deployment and select the later engine version.

    In the Review & Launch step of the Clone Deployment wizard, click Check Deployment so that you can review the configuration of the cloned deployment.

  2. Stop all jobs running pipelines on engines managed by the original deployment.
  3. Stop the original deployment.
  4. Start the new cloned deployment.
  5. Launch engine instances for the new cloned deployment.
  6. Start all jobs that were running on engines managed by the original deployment.

    As long as you assign the same labels to the new cloned deployment, the jobs will start on engines managed by the cloned deployment.

  7. Optionally, delete the original deployment.

Upgrading Engines for Control Hub-Managed Deployments

Use the following steps to upgrade an engine version for a Control Hub-managed deployment, such as an Amazon EC2 or Kubernetes deployment.

  1. Clone the Control Hub-managed deployment and select the later engine version.

    In the Review & Launch step of the Clone Deployment wizard, click Launch and Check Deployment so that you can review the configuration of the cloned deployment after the deployment starts and launches engines on the provisioned resources.

  2. Stop the original deployment.

    As long as you assign the same labels to the new cloned deployment and the jobs are enabled for pipeline failover, the jobs will start on engines managed by the cloned deployment.

    For Data Collector jobs that are not enabled for pipeline failover, synchronize the jobs so that the jobs start on the new Data Collector instances.

    For Transformer jobs that are not enabled for pipeline failover, stop all jobs running pipelines on engines managed by the original deployment. Then start the jobs again so that the jobs start on the new Transformer instances.

  3. Optionally, delete the original deployment.