ApsaraDB for MongoDB:Release the endpoint of a shard or ConfigServer component

Prerequisites

Before you begin, make sure you have:

• A sharded cluster instance that uses the MongoDB protocol

• The account credentials (username and password) for the component — if you have forgotten the password, reset it before proceeding

Considerations

• mongos node endpoints cannot be released. Only shard and ConfigServer component endpoints can be released using this procedure.

• Releasing an endpoint affects all nodes in the component. The endpoints and IP addresses of every node in the component are released simultaneously. Connections to any node via its endpoint are no longer possible.

• ConfigServer endpoints cannot be re-applied. ApsaraDB for MongoDB does not support applying for new ConfigServer endpoints. Once released, a ConfigServer endpoint is permanently unavailable. This does not affect existing ConfigServer endpoints that have not been released.

• This procedure releases only the internal endpoint. To release the public endpoint of a shard or ConfigServer component, see Release a public endpoint.

Release the internal endpoint

1. Go to the Sharded Cluster Instances page. In the top navigation bar, select the resource group and region where the instance is located, then click the instance ID.

2. In the left-side navigation pane, click Database Connections.

3. In the Internal Connections - VPC section, find the target node and click Release in the Actions column.

4. In the Confirm Release dialog, click OK.

Verify the release

The instance status changes from Releasing Connection to Running when the endpoint is successfully released.

What's next

To manage public endpoints for shards or the ConfigServer component, see Release a public endpoint.