Upgrading Engines
Once you save a deployment, you cannot change the engine version. As a result, to upgrade to a newer engine version, you must create a new deployment. At this time, you must manually configure the new deployment to use the same options as the previous deployment.
Upgrading Engines for Self-Managed Deployments
Use the following steps to upgrade an engine version for a self-managed deployment.
-
Create a new self-managed
deployment that uses the new engine version.
- Stop all jobs running pipelines on engines managed by the previous deployment.
- Stop the previous deployment.
- Start the new deployment.
- Launch engine instances for the new deployment.
-
Start all jobs that were running on engines managed by the previous
deployment.
As long as you assign the same labels to the new deployment, the jobs will start on engines managed by the new deployment.
- Optionally, delete the previous 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.
-
For the same parent environment, create a new Control Hub-managed deployment that uses the new engine version.
-
Stop the previous
deployment.
As long as you assign the same labels to the new deployment and the jobs are enabled for pipeline failover, the jobs will start on engines managed by the new 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 previous deployment. Then start the jobs again so that the jobs start on the new Transformer instances.
- Optionally, delete the previous deployment.