On this page本页内容
dropConnections
¶New in version 4.2.版本4.2中的新功能。
The dropConnections
command drops the mongod
/mongos
instance’s outgoing connections to the specified hosts. The dropConnections
must be run against the admin
database.
The command has following syntax:
The command requires the following field:
hostAndPort |
array | Each array element represents the hostname and port of a remote machine. |
comment |
any |
A comment can be any valid BSON type (string, integer, object, array, etc).
|
If the deployment enforces authentication/authorization, the dropConnections
command requires the dropConnections
action on the cluster resource.
Create a user-defined role in the admin
database where the privilege
array includes the following document:
db.createUser()
to create a user on the admin
database with the custom role.
or
db.grantRolesToUser()
to grant the role to an existing user on the admin
database.For example, the following operation creates a user-defined role on the admin
database with the privileges to support dropConnections
:
Assign the custom role to a user on the admin
database:
The created user can execute dropConnections
.
For more examples of user creation, see Add Users. For a tutorial on adding privileges to an existing database user, see Modify Access for an Existing User.
dropConnections
silently ignores hostAndPort
elements that do not include both the hostname and port of the remote machine.
Consider a replica set with a recently removed member at oldhost.example.com:27017
. Running the following dropConnections
command against each active replica set member ensures there are no remaining outgoing connections to oldhost.example.com:27017
:
The command returns output similar to the following:
You can confirm the status of the connection pool for the mongod
or mongos
using the connPoolStats
command.