- Reference >
- Database Commands >
- Diagnostic Commands >
- shardConnPoolStats
shardConnPoolStats¶
On this page
Definition¶
-
shardConnPoolStats
¶ Deprecated since version 4.4: Use
connPoolStats
instead.Returns information on the pooled and cached connections in the sharded connection pool. The command also returns information on the per-thread connection cache in the connection pool.
The
shardConnPoolStats
command uses the following syntax:The sharded connection pool is specific to connections between members in a sharded cluster. The
mongos
instances in a cluster use the connection pool to execute client reads and writes. Themongod
instances in a cluster use the pool when issuingmapReduce
to query temporary collections on other shards.When the cluster requires a connection, MongoDB pulls a connection from the sharded connection pool into the per-thread connection cache. MongoDB returns the connection to the connection pool after every operation.
Output¶
Displays connection status for each config server, replica set, and standalone instance in the cluster.
The number of connections available for this host to connect to the
mongos
.
The number of connections the host has ever created to connect to the
mongos
.
Displays information specific to replica sets.
Holds an array of documents that report on each replica set member. These values derive from the replica set status values.
The host address in the format
[hostname]:[port]
.
This field is for internal use. Reports
false
when themongos
either cannot connect to instance or received a connection exception or error.
The host is the replica set’s primary if this is
true
.
The host is a hidden member of the replica set if this is
true
.
The host is a hidden member of the replica set if this is
true
.The host is a secondary member of the replica set if this is
true
.
The latency, in milliseconds, from the
mongos
to this member.
A
tags
document contains user-defined tag field and value pairs for the replica set member.- For read operations, you can specify a tag set in the read preference to direct the operations to replica set member(s) with the specified tag(s).
- For write operations, you can create a customize write concern using
settings.getLastErrorModes
andsettings.getLastErrorDefaults
.
For more information, see Configure Replica Set Tag Sets.
See also
The number connections in the cluster’s connection pool.
The number of connections to a shard.
The number of connections to a replica set.
The number of connections to the config database.
The number of connections available from the
mongos
to the config servers, replica sets, and standalonemongod
instances in the cluster.
The number of connections the
mongos
has ever created to other members of the cluster.
Displays information on the per-thread connection cache.
Displays each incoming client connection. For a
mongos
, this array field displays one document per incoming client thread. For amongod
, the array displays one entry per incoming shardedmapReduce
client thread.The host using the connection. The host can be a config server, replica set, or standalone instance.
The number of times the host pulled a connection from the pool.
The thread’s availability.
The namespaces used on this connection thus far.