Help Center> GeminiDB> GeminiDB Redis API> Working with GeminiDB Redis API> Instance Changes> Changing the CPU and Memory Specifications of an Instance
Updated on 2024-05-20 GMT+08:00

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.
  • If a dual-active relationship has been created for two instances, do not change their specifications or add or delete nodes to or from them.
  • To view vCPUs and nodes on the Instances page, contact customer service.

Procedure

  1. Log in to the management 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.

    Figure 1 Changing instance specifications

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

    Figure 2 Changing the 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.
    Figure 3 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.