Dataphin:Upgrade Dataphin with zero downtime

Limits

A zero-downtime upgrade is supported only when the first three segments of the current and target version numbers are the same. For example, you can upgrade from V5.1.2.02 to V5.1.2.04.

Prerequisites

• Ensure that you understand the impact of the version upgrade. For more information, see Impact of version upgrades.

• Ensure that no configuration or upgrade is in progress. If an upgrade is in progress, wait for it to complete. If necessary, you can forcibly stop the ongoing upgrade and then try again.

Background information

Upgrading Dataphin with zero downtime involves two main steps: selecting the version and upgrade mode, and then performing the upgrade. During the upgrade, users can log on to Dataphin normally. Dataphin applications are upgraded using a rolling upgrade. The complete flow is shown in the following figure:

Procedure

Step 1: Select the version and upgrade mode

1. Append /opsconsole/v2 to the Dataphin logon URL to open the Dataphin Manager logon page.

2. On the Dataphin Manager logon page, enter the Username and Password, and then click Log On. To obtain the username and password, contact Dataphin operations and maintenance (O&M) personnel.

3. On the Upgrade Records page, click Upgrade Dataphin.

4. On the Upgrade Dataphin page, select the version and upgrade mode. The following table describes the parameters.

   Parameter	Description
   Target version	Select the target version from the version list. If the version list does not contain the target version, click Upload Version Configuration to upload the configuration file for the target version. After the configuration file is uploaded, the system performs a configuration file validation. If the file content is incorrect, the validation fails, and the system reports an error with the failure reason. If the file passes validation and the system does not contain the configuration file for this version, the upload imports the version configuration. If the file passes validation and the system already contains the configuration file for this version, the upload overwrites the system configuration.
   Configuration file	Standard configuration: Click Upload File to upload a configuration file in YAML or ZIP format. After the upload, you can download the configuration file. After the configuration file is uploaded, the system performs a configuration file validation. If the file does not contain all configuration items, the system reports an error. Click View Details in the error message to view the list of Missing Configuration Items. Non-standard configuration: Before you upload the file, contact the Dataphin O&M team to obtain the required configuration file in ZIP format. Click Upload File to upload the obtained file. After the file is uploaded, the system automatically performs the following checks: Checks whether the standard version configuration template (product/dataphin/...) in the configuration file is the same as the uploaded version configuration (consistent MD5 validation). If they are not the same, a message appears indicating that the configuration template in the file is not compatible with the selected version. Confirm with the Dataphin O&M team before you continue the upgrade. Checks whether the overlay file and the values.yaml file are compatible with the standard version configuration template (product/dataphin/...). If they are not compatible, the system blocks the upgrade and a message appears. The message indicates that the configuration information in the file is not compatible with the selected version and the upgrade cannot continue. Confirm with the Dataphin O&M team. Checks whether the values.yaml file in the configuration file is consistent with the values.yaml file running in your current online environment. If they are not consistent, a message appears indicating that the configuration information in the file is inconsistent with the online configuration of the current environment. The upgrade will proceed using the new configuration file. Note Do not use a non-standard configuration unless necessary.
   Upgrade mode	Select Zero-downtime Upgrade. During the upgrade, DataService remains active, and DataService API calls remain available, including synchronous and asynchronous invocations. The system checks the compatibility configuration of the current and target versions to determine if a zero-downtime upgrade is supported. If a zero-downtime upgrade is not supported, a downtime upgrade is selected by default.

5. Select the risk disclaimer checkbox, and then click Start Upgrade.

Step 2: Start the upgrade

The system upgrade progress is shown in a progress bar. During the upgrade, click View Log to view the upgrade log details.