For applications with a large number of read requests, you can create one or more read-only nodes to meet the high demand for database reads and increase application throughput. For detail, refer to Read-only node overview.

How to choose the node specification for a read-only node?

They can be different from the primary node specification, and can also be modified at any time. We recommend that the specification of a read-only node be higher than that of the primary node, or else it can easily result in high delays and high load on the read-only node.

Can the network type of the read-only node be different from that of the primary node?

Currently, only VPC is supported.

Is the account of the read-only node the same as the primary node?

A read-only node can be accessed through the account of the primary node. Both the account and database are synced from the primary node.

How many read-only nodes can I create under a single node?

10.

Why do read-only nodes have no backup function?

Because the primary node already has backups, read-only nodes currently do not support backup settings or manual backup initiation.

Will creating a read-only node affect the primary node?

Creating a read-only node replicates data from the secondary node, so it does not affect the primary node. Any data updates on the primary node will be automatically synced to all the read-only nodes immediately when the operation is completed on the primary node.

Last updated: 2025.11.17 16:15:12

Public security network record in Beijing: No. 11010802032137