Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14046

Investigate changes in SERVER-51499: Separate statistics per ServiceExecutor

      Description

      Downstream Change Summary

      In serverStatus, network.serviceExecutorTaskStats is now network.serviceExecutor with keys broken down by ServiceExecutor.

      Description of Linked Ticket

      The current format does not have allowances for separate service executors. Specifically, we need to represent a new section for the fixed service executor.

      I'm proposing we change from this format:

      "Current format"
      serverStatus: {
          "connections" : {
              "current" : 1,
              "available" : 4,
              "totalCreated" : 1,
              "active" : 1,
              "threaded" : 1,
              "limitExempt" : 1,
              "exhaustIsMaster" : 0,
              "awaitingTopologyChanges" : 0,
              "adminConnections" : {
                  "executor" : "reserved",
                  "threadsRunning" : 3,
                  "readyThreads" : 3,
                  "startingThreads" : 0
              }
          },
          "network" : {
              "serviceExecutorTaskStats" : {
                  "executor" : "passthrough",
                  "threadsRunning" : 1
              }
          }
      }
      

      To this format:

      "New format"
      serverStatus: {
          "connections" : {
              "current" : 1,
              "available" : 4,
              "totalCreated" : 1,
              "active" : 1,
              "threaded" : 1,
              "limitExempt" : 1,
              "exhaustIsMaster" : 0,
              "awaitingTopologyChanges" : 0
          },
          "network" : {
              "serviceExecutorTaskStats" : {
                  "passthrough" : {
                      "threadsRunning" : 1
                  },
                  "fixed" : {
                      "threadsRunning" : 1,
                      "tasksRunning" : 0,
                      "tasksWaiting" : 0
                  },
                  "reserved" : {
                      "threadsRunning" : 3,
                      "readyThreads" : 3,
                      "startingThreads" : 0
                  }
              }
          }
      }
      

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            jason.price@mongodb.com Jason Price
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              3 years, 12 weeks, 3 days ago