Changing vCPUs and Memory

Scenarios

You can change instance vCPUs and memory on the console to accommodate your workloads. If your instance is overloaded, you are advised to add compute nodes.

Usage Notes

• Second-level intermittent disconnection occurs once when the specifications are changed on a single node. Therefore, the entire instance is intermittently disconnected several times. Ensure that the client can be reconnected.
• While specifications of capacity-oriented instances with classic and cloud native storage are being changed, client connections to and traffic of these instances will be taken over by other N – 1 instances. To ensure smooth changes, check the connections and CPU load on other nodes during takeover to avoid latency from too many connections or heavy load.
• You are advised to change the specifications during off-peak hours to avoid instance overload.

Video Tutorial

This video shows how to change instance vCPUs and memory.

Procedure

1. Log in to the GeminiDB console.
2. In the navigation pane, choose Instances.
   • Locate an instance with classic storage. Choose More > Change Specifications in the Operation column.
     Figure 1 Changing specifications
     
   • Locate an instance with cloud native storage, Click Change Specifications in the Operation column.
     Figure 2 Changing instance specifications
     

   In the DB Information area on the Basic Information page, click Change under Node Specifications.

   • Instance with classic storage
     Figure 3 Changing specifications
     
   • Capacity-oriented instance with cloud native storage
     Figure 4 Changing specifications
     

3. 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 10 to 20 minutes. Exercise caution when performing this operation. For your online production services, you are advised to perform the change online.
   • Instance with classic storage
     Figure 5 Changing specifications
     
   • Capacity-oriented instance with cloud native storage
     Figure 6 Changing specifications
     

4. 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.

5. View the change results.

   In the DB Information area on the Basic Information page, you can see the new specifications.

FAQs

What Are the Differences Between Online and Offline Specification Changes of GeminiDB Redis Nodes? How Long Will the Changes Take? What Are the Impacts on Services?