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

Add field to serverStatus that discounts secondary cursors

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Execution

    Description

      "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.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated: