When you no longer need to connect to a shard or Configserver node, you can release its endpoint.
- The endpoint of a mongos node cannot be released.
- After the endpoint of a shard or Configserver node is released, the endpoints of all subnodes in the node are released and this endpoint cannot be used to connect to the node. Proceed with caution.
- This operation releases the internal endpoint of the node. If the node also has a public endpoint and the endpoint is no longer needed, you can release it. For more information, see Release a public endpoint.
- Log on to the ApsaraDB for MongoDB console.
- In the upper-left corner of the page, select the resource group and the region of the target instance.
- In the left-side navigation pane, click Sharded Cluster Instances.
- Find the target instance and click its ID.
- In the left-side navigation pane, click Database Connections.
- In the Internal Connections section, click Release in the Actions column corresponding to a node.
Note The following section describes the node types:
- Mongos: the mongos node
- Shard: the shard node
- CS: the Configserver node
- In the Confirm Release message, click OK.
- Wait until the instance state changes from Releasing Connection to Running.