Serverless clusters support mounting read-only instances to enhance read performance and concurrency while reducing the load on the read-write instance. This document describes how to create a read-only instance and modify its configuration for a serverless cluster.
Billing Description
The read-only and read-write instances have the same billing logic. For more information, see Billing Overview.
Creating Read-Only Instance
Note:
Read-only instance on the current version only supports vertical scaling but not horizontal scaling.
After purchasing a read-only instance group, you can adjust its compute unit and quantity.
The computing power of read-write instances or read-only instances has no impact on each other.
Read-only instances can only be automatically enabled and disabled, and a single instance can't be enabled or disabled manually.
Creating a read-only instance when purchasing a cluster
2. Behind the Serverless Architecture, select the Cluster Edition.
3. Beneath the Read-Only Group, select the number of read-only nodes within the group. You can add a maximum of eight read-only nodes.
4. The configured compute unit range only takes effect for all the read-only nodes in the read-only group.
5. After configuring other configuration items for the serverless clusters, click Buy Now. For more information on the other configuration description of the serverless clusters, see Creating Serverless Cluster.
Adding Read-Only Instances to Existing Serverless Clusters
Note：
You can only perform the operations on the cluster in the running status.
2. Click Target Cluster in the cluster list on the left to enter the cluster management page.
3. On the Cluster Management page, navigate to the Cluster Details section to locate the Read-Only Instance section. Proceed based on the scenarios described.
If the Serverless architecture is deployed in a Single-Node Edition, then in the Read-Only Instance section, click Add Read-Only Instance.
If the Serverless architecture is deployed in a Cluster Edition, click Adjust Configurations in the Read-Only Instance section.
4. Behind the Serverless Architecture, select the Cluster Edition.
5. Select the read-only group, and increase the number of read-only nodes within the read-only group as required. You can add a maximum of eight read-only nodes.
6. Configure the computational power range for the read-only group, which will be effective for all read-only nodes in the group.
7. Click Buy Now to add a read-only instance.
Modifying the configuration of the read-only instance
You can adjust the number of the read-only instances and the compute unit range of the read-only group.
Note：
After adjusting the number of read-only instances, you can manually trigger a load balancing to balance traffic.
You can adjust the number of the read-only instances on the configuration modification page. But you can't add or delete a read-only instance manually.
After the downgrade, the read-only instance will be removed to the recycle bin for isolation and cannot be restored manually there. It can only be restored on the configuration modification page. Isolated read-only instances will still count toward the maximum number (i.e., 8) of read-only instances allowed in a serverless cluster.
When the database proxy is enabled, the business will not be interrupted during the configuration modification.
2. Click the target cluster in the cluster list on the left to enter the cluster management page.
3. Find a read-only instance in the read-only group under Cluster Management page > Cluster Details, click Adjust Configurations after Configuration.
4. You will be redirected to the configuration modification page, select the desired number of read-only nodes and compute unit range to complete the modification.
Yes
No
Was this page helpful?