Database Manual / Reference / Database Commands / Diagnostics

connPoolStats (database command数据库命令)

Definition定义

connPoolStats

The command connPoolStats returns information regarding the open outgoing connections from the current database instance to other members of the sharded cluster or replica set.命令connPoolStats返回有关从当前数据库实例到分片集群或副本集的其他成员的打开的传出连接的信息。

To run connPoolStats, use the db.runCommand( { <command> } ) method.要运行connPoolStats，请使用db.runCommand( { <command> } )方法。

Note

connPoolStats only returns meaningful results for mongos instances and for mongod instances in sharded clusters.仅对分片集群中的mongos实例和mongod实例返回有意义的结果。

Compatibility兼容性

This command is available in deployments hosted in the following environments:此命令在以下环境中托管的部署中可用：

  • MongoDB Atlas: The fully managed service for MongoDB deployments in the cloud：云中MongoDB部署的完全托管服务

Note

This command is supported in all MongoDB Atlas clusters. 所有MongoDB Atlas集群都支持此命令。For information on Atlas support for all commands, see Unsupported Commands.有关Atlas支持所有命令的信息，请参阅不支持的命令。

  • MongoDB Enterprise: The subscription-based, self-managed version of MongoDB：MongoDB的基于订阅的自我管理版本
  • MongoDB Community: The source-available, free-to-use, and self-managed version of MongoDB：MongoDB的源代码可用、免费使用和自我管理版本

Syntax语法

The command has the following syntax:该命令具有以下语法：

db.runCommand(
   {
     connPoolStats: 1
   }
)

The value of the argument (i.e. 1 ) does not affect the output of the command.参数的值（即1）不会影响命令的输出。

Behavior行为

connPoolStats includes aggregated statistics in its output:在其输出中包含聚合统计数据：

  • The hosts field displays the information aggregated by host.hosts字段显示按主机聚合的信息。
  • The pools field displays the information aggregated by pool.pools字段显示按池聚合的信息。

Note

To avoid interference with any running operations, connPoolStats does not take any locks. 为了避免干扰任何正在运行的操作，connPoolStats不接受任何锁。As such, the counts may change slightly as connPoolStats gathers information, resulting in slight differences between the hosts and pools connection counts.因此，随着connPoolStats集合信息，计数可能会略有变化，从而导致hosts和pools连接计数之间的微小差异。

Example示例

The following operation uses the db.runCommand() method to run the connPoolStats command on a mongos of a sharded cluster. 以下操作使用db.runCommand()方法在分片集群的mongos上运行connPoolStats命令。The sharded cluster has 2 shards, each a single-member replica set, and a config server replica set. The mongos runs on a 4-core machine.分片集群有2个分片，每个分片都有一个成员副本集和一个配置服务器副本集。mongos在一台4核机器上运行。

db.runCommand( { "connPoolStats" : 1 } )

The command returns the output of the following form:该命令返回以下形式的输出：

Note

The connPoolStats output varies depending on the deployment and the member against which you run connPoolStats among other factors.connPoolStats的输出因部署和运行connPoolStats的成员以及其他因素而异。

{
   "numClientConnections" : <num>,
   "numAScopedConnections" : <num>,
   "totalInUse" : <num>,
   "totalAvailable" : <num>,
   "totalLeased" : <num>,
   "totalCreated" : <num>,
   "totalRefreshing" : <num>,
   "replicaSetMatchingStrategy" : <string>,
   "acquisitionWaitTimes" : {  // Added in MongoDB 6.3
      "(-inf, 0ms)" : { "count" : <num> },
      "[0ms, 50ms)" : { "count" : <num> },
      "[50ms, 100ms)" : { "count" : <num> },
      "[100ms, 150ms)" : { "count" : <num> },
      "[150ms, 200ms)" : { "count" : <num> },
      "[200ms, 250ms)" : { "count" : <num> },
      "[250ms, 300ms)" : { "count" : <num> },
      "[300ms, 350ms)" : { "count" : <num> },
      "[350ms, 400ms)" : { "count" : <num> },
      "[400ms, 450ms)" : { "count" : <num> },
      "[450ms, 500ms)" : { "count" : <num> },
      "[500ms, 550ms)" : { "count" : <num> },
      "[550ms, 600ms)" : { "count" : <num> },
      "[600ms, 650ms)" : { "count" : <num> },
      "[650ms, 700ms)" : { "count" : <num> },
      "[700ms, 750ms)" : { "count" : <num> },
      "[750ms, 800ms)" : { "count" : <num> },
      "[800ms, 850ms)" : { "count" : <num> },
      "[850ms, 900ms)" : { "count" : <num> },
      "[900ms, 950ms)" : { "count" : <num> },
      "[950ms, 1000ms)" : { "count" : <num> },
      "[1000ms, inf)" : { "count" : <num> },
      "totalCount" : <num>
   },
   "pools" : {
      "NetworkInterfaceTL-TaskExecutorPool-0" : {
         "poolInUse" : <num>,
         "poolAvailable" : <num>,
         "poolLeased" : <num>,
         "poolCreated" : <num>,
         "poolRefreshing" : <num>,
         "acquisitionWaitTimes" : <document>,  // Added in MongoDB 6.3
         "cfg1.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
      },
      "NetworkInterfaceTL-TaskExecutorPool-1" : {
         "poolInUse" : <num>,
         "poolAvailable" : <num>,
         "poolLeased" : <num>,
         "poolCreated" : <num>,
         "poolRefreshing" : <num>,
         "acquisitionWaitTimes" : <document>,  // Added in MongoDB 6.3
         "cfg1.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         }
      },
      "NetworkInterfaceTL-TaskExecutorPool-2" : {
         "poolInUse" : <num>,
         "poolAvailable" : <num>,
         "poolLeased" : <num>,
         "poolCreated" : <num>,
         "poolRefreshing" : <num>,
         "acquisitionWaitTimes" : <document>,  // Added in MongoDB 6.3
         "cfg1.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         }
      },
      "NetworkInterfaceTL-TaskExecutorPool-3" : {
         "poolInUse" : <num>,
         "poolAvailable" : <num>,
         "poolLeased" : <num>,
         "poolCreated" : <num>,
         "poolRefreshing" : <num>,
         "acquisitionWaitTimes" : <document>,  // Added in MongoDB 6.3
         "cfg1.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         }
      },
      "NetworkInterfaceTL-ShardRegistry" : {
         "poolInUse" : <num>,
         "poolAvailable" : <num>,
         "poolLeased" : <num>,
         "poolCreated" : <num>,
         "poolRefreshing" : <num>,
         "acquisitionWaitTimes" : <document>,  // Added in MongoDB 6.3
         "cfg1.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "cfg2.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "cfg3.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "shard1.example.net:27018" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "shard2.example.net:27018" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         }
      },
      "global" : {
         "poolInUse" : <num>,
         "poolAvailable" : <num>,
         "poolLeased" : <num>,
         "poolCreated" : <num>,
         "poolRefreshing" : <num>,
         "acquisitionWaitTimes" : <document>,  // Added in MongoDB 6.3
         "cfg3.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "cfg1.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "cfg2.example.net:27019" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "shard2.example.net:27018" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         },
         "shard1.example.net:27018" : {
            "inUse" : <num>,
            "available" : <num>,
            "leased" : <num>,
            "created" : <num>,
            "refreshing" : <num>,
            "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
         }
      }
   },
   "hosts" : {
      "cfg3.example.net:27019" : {
         "inUse" : <num>,
         "available" : <num>,
         "leased" : <num>,
         "created" : <num>,
         "refreshing" : <num>,
         "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
      },
      "cfg1.example.net:27019" : {
         "inUse" : <num>,
         "available" : <num>,
         "leased" : <num>,
         "created" : <num>,
         "refreshing" : <num>,
         "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
      },
      "cfg2.example.net:27019" : {
         "inUse" : <num>,
         "available" : <num>,
         "leased" : <num>,
         "created" : <num>,
         "refreshing" : <num>,
         "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
      },
      "shard2.example.net:27018" : {
         "inUse" : <num>,
         "available" : <num>,
         "leased" : <num>,
         "created" : <num>,
         "refreshing" : <num>,
         "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
      },
      "shard1.example.net:27018" : {
         "inUse" : <num>,
         "available" : <num>,
         "leased" : <num>,
         "created" : <num>,
         "refreshing" : <num>,
         "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
      }
   },
   "replicaSets" : {
      "csRS" : {
         "hosts" : [
            {
               "addr" : "cfg1.example.net:27019",
               "ok" : <bool>,
               "ismaster" : <bool>,
               "hidden" : <bool>,
               "secondary" : <bool>,
               "pingTimeMillis" : <num>
            },
            {
               "addr" : "cfg2.example.net:27019",
               "ok" : <bool>,
               "ismaster" : <bool>,
               "hidden" : <bool>,
               "secondary" : <bool>,
               "pingTimeMillis" : <num>
            },
            {
               "addr" : "cfg3.example.net:27019",
               "ok" : <bool>,
               "ismaster" : <bool>,
               "hidden" : <bool>,
               "secondary" : <bool>,
               "pingTimeMillis" : <num>
            }
         ]
      },
      "shardB" : {
         "hosts" : [
            {
               "addr" : "shard2.example.net:27018",
               "ok" : <bool>,
               "ismaster" : <bool>,
               "hidden" : <bool>,
               "secondary" : <bool>,
               "pingTimeMillis" : <num>
            }
         ]
      },
      "shardA" : {
         "hosts" : [
            {
               "addr" : "shard1.example.net:27018",
               "ok" : <bool>,
               "ismaster" : <bool>,
               "hidden" : <bool>,
               "secondary" : <bool>,
               "pingTimeMillis" : <num>
            }
         ]
      }
   },
   "ok" : 1,
   "$clusterTime" : {
      "clusterTime" : <timestamp>,
      "signature" : <document>
   },
   "operationTime" : <timestamp>
}

Output输出

connPoolStats.totalAvailable
Reports the total number of available outgoing connections from the current mongod / mongos instance to other members of the sharded cluster or replica set.报告从当前mongod/mongos实例到分片集群或副本集的其他成员的可用传出连接总数。
connPoolStats.totalLeased
Reports the total number of connections borrowed from a pool and expected to return. These connections might not remain active through the duration of a lease, and are excluded from the related metrics. 报告从池中借用并预期返回的连接总数。这些连接可能不会在租赁期间保持活动状态，并被排除在相关指标之外。These connections are unavailble through the duration of the lease.在租赁期间，这些连接是不可用的。
connPoolStats.totalCreated
Reports the total number of outgoing connections ever created by the current mongod / mongos instance to other members of the sharded cluster or replica set.报告当前mongod/mongos实例向分片集群或副本集的其他成员创建的传出连接总数。
connPoolStats.totalInUse
Reports the total number of outgoing connections from the current mongod / mongos instance to other members of the sharded cluster or replica set that are currently in use.报告从当前mongod/mongos实例到当前正在使用的分片集群或副本集的其他成员的传出连接总数。
connPoolStats.totalRefreshing
Reports the total number of outgoing connections from the current mongod / mongos instance to other members of the sharded cluster or replica set that are currently being refreshed.报告从当前mongod/mongos实例到当前正在刷新的分片集群或副本集的其他成员的传出连接总数。
connPoolStats.totalWasNeverUsed
Reports the total number of outgoing connections from the current mongod / mongos instance to other members of the sharded cluster or replica set that were closed having never been used.报告从当前mongod/mongos实例到分片集群或副本集的其他成员的传出连接总数，这些连接是关闭的，从未被使用过。
connPoolStats.replicaSetMatchingStrategy

New in version 5.0.在版本5.0中新增。

On a mongos instance, this value reports the policy used by the instance to determine the minimum size limit of its connection pools to nodes within replica sets.在mongos实例上，此值报告实例用于确定其连接池到副本集中节点的最小大小限制的策略。

On a mongod instance, this value reports the policy used by the instance to determine the minimum size limit of its connection pools to nodes within other replica sets.在mongod实例上，此值报告实例用于确定其连接池到其他副本集中节点的最小大小限制的策略。

The policy for mongos and mongod can be set with the ShardingTaskExecutorPoolReplicaSetMatching parameter.mongos和mongod的策略可以使用ShardingTaskExecutorPoolReplicaSetMatching参数设置。

Note

If the ShardingTaskExecutorPoolReplicaSetMatching is set to "automatic", the replicaSetMatchingStrategy still describes the actual policy being used, not "automatic". 如果ShardingTaskExecutorPoolReplicaSetMatching设置为"automatic"，则replicaSetMatchingStrategy仍描述实际使用的策略，而不是"automatic"。To find the value of the ShardingTaskExecutorPoolReplicaSetMatching, use getParameter which returns the value of the server parameter:要查找ShardingTaskExecutorPoolReplicaSetMatching的值，请使用返回服务器参数值的getParameter：

db.adminCommand( { getParameter : 1, "ShardingTaskExecutorPoolReplicaSetMatching" : 1 } )
connPoolStats.acquisitionWaitTimes

New in version 6.3.在版本6.3中新增。

Document reports a histogram with the wait times for requests to acquire a connection from mongos to mongod:文档报告了一个直方图，其中显示了从mongos到mongod获取连接的请求的等待时间：

  • The document contains time ranges in milliseconds and the number of connection requests in each range.该文档包含以毫秒为单位的时间范围以及每个范围内的连接请求数。
  • -inf is negative infinity and connection requests in the range (-inf, 0ms) did not wait.是负无穷大，范围(-inf, 0ms)内的连接请求没有等待。
  • inf is positive infinity and connection requests in the range [1000ms, inf) waited a time greater than or equal to 1,000 milliseconds.是正无穷大，范围[1000ms, inf)内的连接请求等待的时间大于或等于1000毫秒。
  • totalCount is the total number of connection requests for all time ranges.是所有时间范围的连接请求总数。
"acquisitionWaitTimes" : {
   "(-inf, 0ms)" : { "count" : <num> },
   "[0ms, 50ms)" : { "count" : <num> },
   "[50ms, 100ms)" : { "count" : <num> },
   "[100ms, 150ms)" : { "count" : <num> },
   "[150ms, 200ms)" : { "count" : <num> },
   "[200ms, 250ms)" : { "count" : <num> },
   "[250ms, 300ms)" : { "count" : <num> },
   "[300ms, 350ms)" : { "count" : <num> },
   "[350ms, 400ms)" : { "count" : <num> },
   "[400ms, 450ms)" : { "count" : <num> },
   "[450ms, 500ms)" : { "count" : <num> },
   "[500ms, 550ms)" : { "count" : <num> },
   "[550ms, 600ms)" : { "count" : <num> },
   "[600ms, 650ms)" : { "count" : <num> },
   "[650ms, 700ms)" : { "count" : <num> },
   "[700ms, 750ms)" : { "count" : <num> },
   "[750ms, 800ms)" : { "count" : <num> },
   "[800ms, 850ms)" : { "count" : <num> },
   "[850ms, 900ms)" : { "count" : <num> },
   "[900ms, 950ms)" : { "count" : <num> },
   "[950ms, 1000ms)" : { "count" : <num> },
   "[1000ms, inf)" : { "count" : <num> },
   "totalCount" : <num>
}
connPoolStats.numClientConnection

Reports the number of active and stored outgoing synchronous connections from the current mongod / mongos instance to other members of the sharded cluster or replica set.报告从当前mongod/mongos实例到分片集群或副本集的其他成员的活动和存储的传出同步连接的数量。

These connections are a part of a pool that is a subset of the data reported by totalAvailable, totalCreated, and totalInUse.这些连接是池的一部分，池是totalAvailable、totalCreated和totalInUse报告的数据的子集。

connPoolStats.numAScopedConnection

Reports the number of active and stored outgoing scoped synchronous connections from the current mongod / mongos instance to other members of the sharded cluster or replica set.报告从当前mongod/mongos实例到分片集群或副本集的其他成员的活动和存储的传出作用域同步连接的数量。

These connections are a part of a pool that is a subset of the data reported by totalAvailable, totalCreated, and totalInUse.这些连接是池的一部分，池是totalAvailable、totalCreated和totalInUse报告的数据的子集。

connPoolStats.pools

Reports on connection statistics (in use/available/created/refreshing) grouped by the connection pools. 按连接池分组的连接统计数据（使用中/可用/创建/刷新）报告。A mongod or mongos has two distinct families of outgoing connection pools:mongod或mongos有两个不同的传出连接池家族：

  • DBClient-based pools (the "write path") and基于DBClient的池（“写入路径”）和
  • NetworkInterfaceTL-based pools (the "read path").基于NetworkInterfaceTL的池（“读取路径”）。

For each pool, the command returns a document that resembles the following:对于每个池，该命令返回一个类似于以下内容的文档：

{
  "poolInUse" : <num>,
  "poolAvailable" : <num>,
  "poolLeased" : <num>,
  "poolCreated" : <num>,
  "poolRefreshing" : <num>,
  "acquisitionWaitTimes" : <document>,  // Added in MongoDB 6.3
  "[host1]" : {
     "inUse" : <num>, "available" : <num>, "leased" : <num>, "created" : <num>, "refreshing" : <num>,
     "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
  },
  "[host2]" : {
     "inUse" : <num>, "available" : <num>, "leased" : <num>, "created" : <num>, "refreshing" : <num>,
     "acquisitionWaitTimes" : <document>  // Added in MongoDB 6.3
  },
  ...
}

Note

If there are no connections (in use/available/created/refreshing) for a particular pool, the connPoolStats does not return statistics for that pool.如果特定池没有连接（正在使用/可用/创建/刷新），connPoolStats不会返回该池的统计信息。

connPoolStats.pools.NetworkInterfaceTL-TaskExecutorPool-[n]

Displays connection statics related to TaskExecutor pools. Typically, there will be one TaskExecutorPool per core, e.g. pools.NetworkInterfaceTL-TaskExecutorPool-0 ... pools.NetworkInterfaceTL-TaskExecutorPool-7 for an 8-core processor.显示与TaskExecutorPool相关的连接统计信息。通常，每个核心将有一个TaskExecutorPool，例如pools.NetworkInterfaceTL-TaskExecutorPool-0...pools.NetworkInterfaceTL-TaskExecutorPool-7用于8核处理器。

Tip

taskExecutorPoolSize

connPoolStats.pools.NetworkInterfaceTL-ShardRegistry

Available if the command is run on a member of a sharded cluster.如果该命令在分片集群的成员上运行，则可用。

Displays the pool statistics for the connections between the current mongod / mongos instance and other members of the sharded cluster.显示当前mongod/mongos实例与分片集群其他成员之间连接的池统计信息。

connPoolStats.pools.NetworkInterfaceTL-Replication

Available if the command is run on a member of a replica set.如果在副本集的成员上运行该命令，则可用。

Displays the pool statistics for the connections between the current mongod instance and the other members of the replica set.显示当前mongod实例与副本集其他成员之间连接的池统计信息。

connPoolStats.pools.global
Displays the DBClient-based pool statistics.显示基于DBClient的池统计信息。
connPoolStats.pools.[pool].poolWasNeverUsed
Displays the number of connections in this connection pool that were closed having never been used.显示此连接池中已关闭但从未使用过的连接数。
connPoolStats.pools.[pool].acquisitionWaitTimes

New in version 6.3.在版本6.3中新增。

Reports the wait times for requests to acquire a connection from mongos to mongod. 报告从mongos到mongod获取连接的请求的等待时间。For details, see connPoolStats.acquisitionWaitTimes.有关详细信息，请参阅connPoolStats.acquisitionWaitTimes。

connPoolStats.hosts

Reports on connection statistics (in use/available/created/refreshing) grouped by the hosts.按主机分组的连接统计数据（使用中/可用/创建/刷新）报告。

Contains documents that represent a report of connections between the current mongod / mongos instance and each member of the sharded cluster or replica set.包含表示当前mongod/mongos实例与分片集群或副本集的每个成员之间的连接报告的文档。

connPoolStats.hosts.[host].available
Reports the total number of connections available for connecting to the [host].报告可用于连接到[host]的连接总数。
connPoolStats.hosts.[host].leased
Reports the total number of connections to the host borrowed from a pool and expected to return. These connections might not remain active through the duration of a lease, and are excluded from the related metrics. These connections are unavailble through the duration of the lease.报告从池中借用并预期返回的主机连接总数。这些连接可能不会在租赁期间保持活动状态，并被排除在相关指标之外。在租赁期间，这些连接是不可用的。
connPoolStats.hosts.[host].created
Reports the number of connections to the [host] ever created.报告已创建的与[host]的连接数。
connPoolStats.hosts.[host].inUse
Reports the number of connections to the [host] that are currently in use.报告当前正在使用的与[host]的连接数。
connPoolStats.hosts.[host].wasNeverUsed
Reports the total number of outgoing connections from host to other members of the sharded cluster or replica set that were closed having never been used.报告从host到分片群集或副本集的其他成员的传出连接总数，这些连接是关闭的，从未被使用过。
connPoolStats.hosts.[host].acquisitionWaitTimes

New in version 6.3.在版本6.3中新增。

Reports the wait times for requests to acquire a connection from mongos to mongod. 报告从mongos到mongod获取连接的请求的等待时间。For details, see connPoolStats.acquisitionWaitTimes.有关详细信息，请参阅connPoolStats.acquisitionWaitTimes。

connPoolStats.replicaSets

Contains documents that represent a report of information related to each replica set connected to the current mongod / mongos.包含表示与连接到当前mongod/mongos的每个副本集相关的信息报告的文档。

connPoolStats.replicaSets.replicaSet
Reports on each replica set connected to the current mongod / mongos.报告连接到当前mongod/mongos的每个副本集。
connPoolStats.replicaSets.[replicaSets].hosts

Holds an array of documents that reports on each member in the replica set.保存一组报告副本集中每个成员的文档。

These values derive from the replica set status values.这些值来源于副本集状态值。

connPoolStats.replicaSets.[replicaSet].hosts[n].addr
Reports the address for the member in the replica set in [hostname]:[port] format.以[hostname]:[port]格式报告副本集中成员的地址。
connPoolStats.replicaSets.[replicaSet].hosts[n].ok

Reports false when:在以下情况下报告false：

  • the current mongos or mongod cannot connect to instance.当前的mongos或mongod无法连接到实例。
  • the current mongos or mongod received a connection exception or error.当前的mongos或mongod收到连接异常或错误。

This field is for internal use.此字段供内部使用。

connPoolStats.replicaSets.[replicaSet].hosts[n].ismaster
Reports true if this host is the primary member of the replica set.如果此host是副本集的primary，则报告为true。
connPoolStats.replicaSets.[replicaSet].hosts[n].hidden
Reports true if this host is a hidden member of the replica set.如果此host是副本集的隐藏成员，则报告为true。
connPoolStats.replicaSets.[replicaSet].hosts[n].secondary
Reports true if this host is a secondary member of the replica set.如果此host是副本集的secondary成员，则报告为true。
connPoolStats.replicaSets.[replicaSet].hosts[n].pingTimeMillis
Reports the ping time in milliseconds from the mongos or mongod to this host.报告从mongos或mongod到此host的ping时间（毫秒）。
connPoolStats.replicaSets.[replicaSet].hosts[n].tags
Reports the members[n].tags, if this member of the set has tags configured.如果集合中的此成员配置了标签，则报告members[n].tags。

See also Response for details on the ok status field, the operationTime field and the $clusterTime field.有关ok状态字段、operationTime字段和$clusterTime字段的详细信息，请参阅响应。

host