Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21597

Fix connPoolStats command to work with many TaskExecutor-NetworkInterface pairs

    • Minor Change
    • ALL
    • Platform D (12/11/15), Platforms E (01/08/16)

      With the completion of SERVER-20944 the results of the connPoolStats command are no longer correct. The command must be changed to collect statistics from all executors in the TaskExecutor pool, for sharded systems. Rather than reporting on each connection pool individually, since many of these pools are sharing workloads, connPoolStats should aggregate and report information from all connection pools within the server.

      This work changes the output format of the command to the following:

              "numClientConnections" : 22,
              "numAScopedConnections" : 0,
              "totalInUse" : 1,
              "totalAvailable" : 2,
              "totalCreated" : 3,
              "hosts" : {
                      "localhost:27018" : {
                              "inUse" : 0,
                              "available" : 2,
                              "created" : 2
                      "localhost:27017" : {
                              "inUse" : 1,
                              "available" : 0,
                              "created" : 1
              "replicaSets" : {
              "ok" : 1

      This new format is similar to the 3.0 formatting, but differs in the following ways:

      • the reported stats are aggregated across all connection pools in the server
      • the createdByType field has been removed (see SERVER-20283)
      • a new field, totalInUse, reports the number of connections currently in use across all pools
      • within each host's stats, the new inUse field reports the number of connections currently in use across all pools for this particular host

      SERVER-21674 documents a possible future feature to report connection stats separately for each connection pool instead of aggregating these statistics.

            samantha.ritter@mongodb.com Samantha Ritter (Inactive)
            samantha.ritter@mongodb.com Samantha Ritter (Inactive)
            0 Vote for this issue
            5 Start watching this issue