When you no longer need to connect to a shard or Configserver node, you can release its endpoint.

Precautions

  • 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.

Procedure

  1. Log on to the ApsaraDB for MongoDB console.
  2. In the upper-left corner of the page, select the resource group and the region of the target instance.
  3. In the left-side navigation pane, click Sharded Cluster Instances.
  4. Find the target instance and click its ID.
  5. In the left-side navigation pane, click Database Connections.
  6. 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
  7. In the Confirm Release message, click OK.
  8. Wait until the instance state changes from Releasing Connection to Running.