ApsaraDB for MongoDB:Release the endpoint of a shard or ConfigServer node in a sharded cluster instance

Limits

• The endpoint of a mongos node cannot be released.

• Before you release the endpoint of a shard or ConfigServer node in a sharded cluster instance, keep the account and password of the node. This is because ApsaraDB for MongoDB only allows you to specify the account and password of a node when you apply for an endpoint for the first time.

• When the system releases the endpoint of a shard or ConfigServer node in a sharded cluster instance, the system releases the endpoints and IP addresses of all subnodes in the node and you can no longer connect to the node by using the endpoint. Proceed with caution.

• The procedure in this topic releases only the internal endpoint of a shard or ConfigServer node in a sharded cluster instance. To release the public endpoint of a shard or ConfigServer node in a sharded cluster instance, see Release a public endpoint.

Procedure

1. Log on to the ApsaraDB for MongoDB console.

2. In the left-side navigation pane, click Sharded Cluster Instances.

3. In the upper-left corner of the page, select the resource group and region to which the instance belongs.

4. Click the ID of an instance, or click in the Actions column corresponding to the instance and select Manage.

5. In the left-side navigation pane of the instance details page, click Database Connections.

6. In the Internal Connections - VPC section, find the node whose endpoint you want to release and click Release in the Actions column.

   The node types in a sharded cluster instance:

   • Mongos: mongos node

   • Shard: shard node

   • CS: ConfigServer node

7. In the Confirm Release message, click OK.

   When the instance state changes from Releasing Network Connection to Running, the endpoint is released.