When the number of connections reaches its limit or there is a performance problem, you can manually restart an instance.

Considerations

• Restarting an instance leads to the rotary restart of instance nodes. Before the restart, make sure that you have arranged your business correctly and the application can be reconnected.
• Restarting a replica cluster instance may cause the switch between master and slave nodes and the change in the role of a connecting node. It is recommended that you use the Connection string address to connect to the master and slave nodes of the instance, avoiding a negative effect to the read and write operation.
• You can restart a specified sharded cluster instance, and also restart any Mongos node or Shard node in a sharded cluster instance.

Restart an Instance

1. Log into the MongoDB management console.
2. In the upper left corner of the page, select the region where the instance resides.
3. In the left navbar, click the Replica Cluster Instance List or Sharded Cluster Instance List.
4. Find the target instance in the instance list and click Start in the Action Bar.

Restart Nodes in Sharded Cluster Instances

1. Log in to the MongoDB management console.
2. In the upper left corner of the page, select the region where the instance resides.
3. In the left navigation bar, click the Sharded Cluster Instance List.
4. In the Mongos list or Shard list, find the target node and click Restart on the Action Bar.