ApsaraDB RDS:Add instance nodes

Billing rules

For more information about the billing rules after nodes are added, see Specification changes.

Add a regular node

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. On the Basic Information page, in the Instance Topology Management section, click Add or Delete Node.

3. In the dialog box, select Add Node and click Next.

4. In the Nodes section, click the icon or Add Node, and then configure the zone, instance type, and vSwitch for the new node as needed.

   Note

   To cancel adding the new node, you can click the icon to the left of the node.

5. Read the terms of service and click Pay Now.

   The node is added when the instance status changes from Adding Node to Running.

Add a DuckDB analytical read-only node

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. On the Basic Information page, in the Instance Topology Management section, click Add or Delete Node.

3. In the dialog box, select Add read-only nodes for DuckDB analysis and click Next.

4. Configure the DuckDB analytical read-only node. The following table describes the key parameters.

   Parameter	Description
   Billing Method	Both subscription and pay-as-you-go are supported. The Serverless option is not supported.
   Edition	Only High-availability Edition is supported.
   Storage Type	Same as the primary instance.
   Product Type	Only Standard is supported.
   Zone of Primary Node	You can select only a zone within the region of the primary instance.
   Deployment Method	Single-zone Deployment: The primary and secondary nodes are deployed in the same zone. Multi-zone Deployment: The primary and secondary nodes are deployed in different zones within the same region. This provides cross-zone disaster recovery at no extra cost. If you select this mode, you must also configure a zone for the secondary node.
   Instance Type	Dedicated instance types are supported. For more information, see DuckDB analytical read-only instance types.
   Database Proxy	When enabled, the General-purpose database proxy (free of charge) automatically splits HTAP-based requests. OLAP queries are routed to the DuckDB analytical read-only node, and OLTP queries are routed to the primary instance or regular read-only instances.
   Storage Capacity	The analytical read-only node's storage space must be at least half that of the primary instance.

5. Click Next: Instance Configuration and configure the network and resource group for the instance. The following table describes the key parameters.

   Parameter	Description
   VPC	Defaults to the VPC of the primary instance and cannot be changed.
   VSwitch of Primary Node	Use the default vSwitch for the primary node or select a different one.
   Resource Group	Defaults to the resource group of the primary instance and cannot be changed.

6. Click Next: Confirm Order.

7. Confirm the Parameter Configuration, specify the Quantity, and click Pay Now.

   If you select the subscription billing method, you must also specify the Duration. We recommend that you select Auto-renewal to prevent service disruptions caused by an expired subscription.

8. After a short wait, find the primary instance in the Instances. Click the drop-down arrow to the left of the instance ID to view the DuckDB analytical read-only node under it.

Related operations

• After you add the node, you can configure the weight of the cluster's read-only endpoint to distribute traffic to the new node for load balancing.

• Add a node to a primary ApsaraDB RDS for MySQL cluster by calling the CreateDBNodes API operation.