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.
- When the endpoint of a shard or Configserver node is released, the endpoints and IP addresses of all subnodes in the node are released and you can no longer connect to the node by using the endpoint. 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 left-side navigation pane, click Sharded Cluster Instances.
- In the upper-left corner of the page, select the resource group and region to which the instance belongs.
- Click the ID of an instance, or click in the Actions column corresponding to the instance and select Manage.
- In the left-side navigation pane of the instance details page, click Database Connections.
- In the Internal Connections - VPC section, find the node whose endpoint you want to release and click Release in the Actions column. 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. When the instance state changes from Releasing Network Connection to Running, the endpoint is released.