Tencent Cloud

Recent Pages

Restarting a Node

Last updated: 2024-10-10 11:47:15

Overview
In daily Ops, restarting nodes helps free up memory or clear caches, optimizing resource usage. When a node experiences a failure, restarting it can assist in restoring service.
Must-Knows
Restarting a node will disconnect existing connections, so ensure that your application has a reconnection mechanism in place.
Restarting the primary node will trigger a primary-secondary switch, and there is a risk of data loss if unsynchronized data has not been replicated to the secondary node. Assess the risks carefully.
Prerequisite
Instance status should be Running.
Restarting Mongod Node
1. Log in to the MongoDB Console.
2. In the left sidebar, choose Replica Set Instance or Shard Instance from the MongoDB dropdown.
3. At the top of the Instance List page on the right, select the region.
4. In the instance list, find the target instance for which you want to view the node.
5. Click the instance ID to enter the Instance Details page, and click the Node Management tab.
6. On the Node Management page, under the Mongod Node tab, locate the node you want to restart in the node list.
7. In the Operation column, click Restart.
Replica set
﻿
Sharded instance
﻿
8. In the Restart Mongod Node popup window, view the must-knows, check the box for Confirm the risk of restarting the node, and click OK.
﻿
9. Wait for the task to be completed.
Restarting ConfigServer Node
1. Log in to the MongoDB Console.
2. In the left sidebar, select Replica Set Instance or Shard Instance from the MongoDB dropdown.
3. At the top of the Instance List page on the right, select the region.
4. In the instance list, find the target instance for which you want to view the node.
5. Click the instance ID to enter the Instance Details page, and click the Node Management tab.
6. On the Node Management page, under the ConfigServer Node tab, locate the node you want to restart in the node list.
7. In the Operation column, click Restart.