Upgrading Components in Batches

Prerequisites

The component status is Running, Not ready, or Abnormal. For details about how to check the component status, see Viewing Component Details.

If the component is deployed based on a container, it is recommended that the total number of component instances to be upgraded in batches be less than or equal to 30. Otherwise, CCE will limit the traffic and the upgrade will take a long time.

Upgrading Components in Batches

1. Log in to ServiceStage.
2. Choose Application Management.
3. Click the application where the target components are located. The Overview page of the application is displayed.
4. Select the components to be upgraded in batches in Component List and click Bulk Upgrade.
5. Set the version configuration information of the components to be upgraded by referring to the following table.

   Parameter	Description
   Component Version	Target version of the upgraded component. By default, the version number is the time when you start to upgrade the component. The format is yyyy.mmdd.hhmms, where s is the ones place of the second in the timestamp. For example, if the timestamp is 2022.0803.104321, the version number is 2022.0803.10431. You can also customize the version number in the format of A.B.C, or A.B.C.D. A. B, C, and D are natural numbers, for example, 1.0.0 or 1.0.0.0. NOTICE: The customized version number must be unique and cannot be the same as any historical version number of the component. Otherwise, the current deployment record will overwrite the historical deployment record of the same version.
   Image Package	Click . Select the component source again. For details, see Component Source. If the component is deployed in a container, you can custom a container name. The name contains 1 to 63 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.
   Deployment Batch	Number of batches in which component instances are upgraded. The value range is [1, Total number of instances]. Total number of instances refers to the number of running instances of the component. For example, if there are 4 component instances and Deployment Batch is set to 2, these component instances are upgraded in two batches, and each batch involves two component instances.

6. Click Advanced Settings in the Operation column of a container-deployed component to configure advanced settings.
   • Set Cloud Service Settings by referring to Managing Cloud Service Settings of a Container-Deployed Component.
   • Set Container Settings by referring to Managing Container Settings of a Container-Deployed Component.
   • Set Advanced Settings by referring to Managing Advanced Settings of a Container-Deployed Component.

7. (Optional) Click Pre-check Advanced Settings to check whether the advanced settings of each component are correct.

   For example, if the component has been bound to a specified microservice engine, distributed cache, or cloud database instance but the specified instance is not bound to the environment to which the component belongs, an error is reported during advanced settings pre-check. Perform the following operations to reconfigure the parameters and then continue:

   1. In the displayed dialog box, confirm the information and click OK.
   2. Click Advanced Settings in the Operation column of the component for which the error is reported.
   3. Reset the advanced settings of the component based on the error information by referring to 6.

8. Click Complete and Execute. The system automatically checks whether the advanced settings of each component are correct.
   • If no, reset the advanced settings of the component based on the error information by referring to 6.
   • If yes, wait until the component status changes from Upgrading/Rolling back the component to Running, indicating that the component version configuration is successfully upgraded.

Follow-Up Operations