Upgrading a Minor Engine Version

Precautions

• A DDS version cannot be downgraded, for example, from 4.0 to 3.4.
• Pay attention to patches that address issues and vulnerabilities from the open source community. When a new patch is released, install the patch in a timely manner.
• During the upgrade, your services may be intermittently interrupted once for up to 30s for each node. Ensure that your instance can be reconnected automatically or perform this operation during off-peak hours.
• DDL operations, such as create event, drop event, and alter event, are not allowed during the upgrade.

Constraints

• Only cluster and replica set instances support minor engine version upgrade.
• The instance version must be 3.4, 4.0, or 4.2.
• If the instance status is abnormal or the instance is being operated, the upgrade cannot be performed.
• The upgrade cannot be performed if the instance nodes are abnormal.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click in the upper left corner of the page and choose Databases > Document Database Service.
4. On the Instances page, locate the instance you want to upgrade and click Upgrade Minor Version in the DB Engine Version column.
   Figure 2 Minor version upgrade
   

   Alternatively, click the instance. In the DB Information area on the Basic Information page, click Upgrade Minor Version in the DB Engine Version field.

   Figure 3 Minor version upgrade
   

5. In the displayed dialog box, specify Scheduled Time based on service requirements and click OK. You can view the upgrade progress on the Task Center page.
   • Minimum downtime: The upgrade has little impact on services.
   • Fastest completion: The upgrade takes a relatively short time.
   Figure 4 Selecting a scheduled time
   
   

   The time required for the upgrade varies according to the site requirement.