Skip to main content
Delphix

Changes to upgrade behavior from version 18.0.0.0/18.0.0.1 to 19.0.0.0 (KBA10709)

 

 

KBA

KBA#
10709

 

Overview

Release 18.0.0.0 of the Continuous Data engine brought changes to the upgrade process (see Decreased VDB Downtime in the Release 18.0.0.0 - New features section of the release notes).

As a result, the engine may appear to behave differently during the upgrade process when compared with previous versions. This article has been created to explain the process further.

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Date Release
Dec 20, 2023 | Jan 10, 2024 18.0.0.0 | 18.0.0.1

Understanding changes to the upgrade process

Note - This behaviour will only be present in upgrades from 18.0.0.0/18.0.0.1 -> 19.0.0.0. 

If you choose the Apply Now (see Upgrading the Delphix Engine: Overview) option, as a result of the Decreased VDB Downtime changes, the upgrade process now effectively carries out a deferred/Delay the Reboot upgrade, then immediately carries out the finish deferred/Finalize upgrade afterwards. 

This reduces the amount of time that VDBs are unavailable, as they are only quiesced during the second stage of the process (previously they would have been quiesced at the start of the upgrade process).

As a result, there may be occasions during the upgrade where the engine behaves in an unexpected fashion.

Scenario 1 - Management Service State STARTING UP

After the engine has completed the initial (deferred) upgrade step, if your browser refreshes before the management service is back online, you may see a similar message to this screenshot in the browser page:

Screenshot 2024-01-18 at 11.55.25.png

This is expected. The message will remain until the management service has fully come back online, at which time you will see the login page.

Scenario 2 - Reboot after logging in

After the initial upgrade step has completed, if you login to the engine, you may find that the engine very quickly reboots or is already in the process of rebooting.

Again this is expected, especially if there are a small number of VDBs on the engine and the quiesce process completes quickly.

Please wait until the engine has rebooted fully. Once complete you will see the login page again.