Changing the CPU and Memory Specifications of an Instance

Scenarios

You can increase or decrease the CPU or memory of all nodes in an instance. You can change the vCPU and memory specifications of your instance to meet your service requirements. If an instance is overloaded and compute resources need to be added urgently, you are advised to add compute nodes first.

Precautions

• During online specification change, second-level intermittent disconnection occurs once when the change is performed on a single node. Therefore, the entire instance is intermittently disconnected for several times. The client must have an automatic reconnection mechanism. You are advised to perform the specification change during off-peak hours.
• For a node whose specifications are being changed, its computing tasks are handed over to other nodes. Change specifications of nodes during off-peak hours to prevent the instance from overload.
• To modify specifications of an instance based on another specification ratio, contact customer service.
• After specifications of a standard instance in cloud native deployment mode are changed, the system automatically adjusts the storage capacity to the number of shards multiplied by shard specifications (GB).

Procedure

1. Log in to the GeminiDB console.
2. In the service list, choose Databases > GeminiDB Redis API.
3. On the Instances page, locate the instance whose specifications you want to change and click More > Change Specifications in the Operation column.
   • Instance in classic deployment mode
     Figure 1 Changing specifications
     
   • Instance in cloud native deployment mode
     Figure 2 Changing specifications
     

   In the DB Information area on the Basic Information page, click Change next to the Specifications field.

   • Instance in classic deployment mode
     Figure 3 Changing specifications
     
   • Capacity-oriented instance in cloud native deployment mode
     Figure 4 Changing specifications
     
   • Standard instance in cloud native deployment mode
     Figure 5 Changing specifications
     

4. On the displayed page, select a specification change mode and required specifications, and click Next.
   • Online change: During the change, instance nodes are upgraded in rolling mode, which has the minimum impact on services. The change duration is positively related to the number of nodes. Each node takes about 5 to 10 minutes. If there are a large number of nodes, wait patiently.
   • Offline change: During offline change, all nodes are changed concurrently, which interrupts services for about 10 to 20 minutes. Exercise caution when performing this operation. For your online production services, you are advised to perform the change online.
   • Instance in classic deployment mode
     Figure 6 Changing specifications
     
   • Capacity-oriented instance in cloud native deployment mode
     Figure 7 Changing specifications
     
   • Standard instance in cloud native deployment mode
     Figure 8 Changing specifications
     

5. On the displayed page, confirm the specifications.
   • If you need to modify your settings, click Previous.
   • If you do not need to modify your settings, click Submit .

6. View the results.

   Go to the Basic Information page and in the DB Information area you can see the new instance specifications.