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

Add field to serverStatus that discounts secondary cursors

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Query Execution

      "cursor" : { 
           "timedOut" : NumberLong(<num>), 
            "open" : { 
                      "noTimeout" : NumberLong(<num>), 
                       "pinned" : NumberLong(<num>), 
                       "multiTarget" : NumberLong(<num>), 
                       "singleTarget" : NumberLong(<num>), 
                        "total" : NumberLong(<num>), } } 
      

      We'd like some way to distinguish client cursors from secondary cursors. Charlie suggested this could be accomplished by discounting oplog cursors while still including change streams. We will have some false negatives, but I expect this new field to be more representative of client activity than the current field.

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            alyson.cabral@mongodb.com Alyson Cabral (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: