ApsaraDB for MongoDB automatically configures replica sets for instances so that you can manage the primary and secondary nodes. Advanced functions such as disaster recovery and failover are available after instances are created. When you use the instances, these functions are triggered without you knowing about it.
- Primary node: All read and write operations are performed on the primary node. Each replica set instance contains only one primary node.
- Secondary node: The data of a secondary node is synchronized with the primary node
by using oplogs. If the primary node fails, a secondary node can be elected as the
new primary node to ensure high availability.
Note When you connect to an instance by using the endpoint of a secondary node, you can only read data from the instance but cannot write data to it.
- Hidden node: The data of a hidden node is synchronized with the primary node by using
oplogs. If a secondary node fails, the hidden node can be elected as the new secondary
node to ensure high availability.
Note The hidden node is used only to ensure high availability and is not visible to users.
Scale out nodes in a replica set instance
ApsaraDB for MongoDB allows you to scale out the number of nodes in an instance. You can increase the number of secondary nodes based on your business needs. For more information, see Change the number of nodes for a replica set instance.
For example, assume that you are running an informational website or an order query system that has more read operations than write operations. To improve the read performance, you can add secondary nodes. You can also add secondary nodes during business spikes and remove unnecessary nodes to save costs after the spikes.