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

Investigate changes in SERVER-51730: Report histogram data on how long it takes cursors to drain

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc0
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Downstream Change Summary

      Added a new server status metric to count the number of cursors with lifespans between pre-defined lifespan buckets. The buckets are 0s - 1s, 1s - 5s, 5s - 15s, 15s - 30s, 30s - 1m, 1m - 10m, and >= 10m. The ranges exclude the lower number include the upper number (so 1s - 5s means 1s < t <= 5s).

      The names of these buckets are:

      "cursor.lifespan.lessThan1Second", "cursor.lifespan.lessThan5Seconds", "cursor.lifespan.lessThan15Seconds", "cursor.lifespan.lessThan30Seconds", "cursor.lifespan.lessThan1Minute", "cursor.lifespan.lessThan10Minutes", "cursor.lifespan.greaterThanOrEqual10Minutes",

      Description of Linked Ticket

      Report histogram data in serverStatus on cursor drain times (i.e. the time from when a cursor is created to when it is exhausted or killed).

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                26 weeks ago
                Date of 1st Reply: