Upgrading a Minor Version
GeminiDB Cassandra can be upgraded by installing patches to improve performance, release new features, or fix bugs.
If a new patch is released, you can upgrade your instance by clicking the upgrade button in the Compatible API column on the Instances page.
Precautions
- Upgrade your instance once there are new patches released.
- The instance will be restarted and services may be interrupted during the upgrade. The interruption duration depends on services, quantity of nodes, and the amount of service data. Upgrade your instance during off-peak hours.
- When you upgrade a cluster, services may be interrupted a number of times equal to the number of nodes in the cluster plus one. Each interruption will last for no more than a minute and will only affect the services on that node. The upgrade duration is as follows:
600 + (N x 60) ≤ Total upgrade duration (s) ≤ 600 + (N x 120)
For example, if there are 9 nodes in a cluster instance, the upgrade duration is 19 to 28 minutes.
The upgrade duration of most instances is close to 600+ (N x 60). If there are too many tokens on a single node, the upgrade duration may be increased.
- Before you upgrade a DR instance, upgrade the corresponding standby instance first and then the primary instance afterwards.
Procedure
- Log in to the management console.
- In the service list, choose Databases > GeminiDB.
- On the Instances page, locate the instance you want to upgrade and click Upgrade Minor Version in the Compatible API column.
Figure 2 Patch installation
Alternatively, click the instance name to go to the Basic Information page. In the DB Information area, click Upgrade Minor Version in the Compatible API field.
Figure 3 Patch installation
- In the displayed dialog box, click OK.
Figure 4 Confirming dialog box
- View the upgrade result on the Instances page.
- When the upgrade is ongoing, the instance status is Upgrading minor version.
- After the upgrade is complete, the instance status changes Available.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.