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

Inconsistent getMore logging

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • None
    • Query

      As of 3.2.8 I can see at least three different types of getMore commands that can be logged:

      "getMore on an aggregation cursor"
      2016-08-17T05:30:55.215+0000 I COMMAND  [conn117464] getmore test.col query: { aggregate: "col", pipeline: [], fromRouter: true, cursor: { batchSize: 0 } } cursorid:4426089
      5558 ntoreturn:0 cursorExhausted:1 keyUpdates:0 writeConflicts:0 numYields:3 nreturned:406 reslen:13418 locks:{ Global: { acquireCount: { r: 12 } }, Database: { acquireCoun
      t: { r: 6 } }, Collection: { acquireCount: { r: 6 } } } 126ms
      
      "getMore on a regular query"
      2016-08-15T14:42:12.291-0400 I COMMAND  [conn616] getmore NAD.products cursorid:64166768643 ntoreturn:0 exhaust:1 keyUpdates:0 writeConflicts:0 numYields:5 nreturned:731 reslen:4197830 locks:{ Global: { acquireCount: { r: 12 } }, Database: { acquireCount: { r: 6 } }, Collection: { acquireCount: { r: 6 } } } 16ms
      "getMore on a tailable cursor"
      2016-08-15T16:25:01.642-0400 I COMMAND  [conn9] command local.oplog.rs command: getMore { getMore: 19848245430, collection: "oplog.rs", maxTimeMS: 5000, term: 1, lastKnownCommittedOpTime: { ts: Timestamp 1471286528000|1, t: 1 } } cursorid:19848245430 keyUpdates:0 writeConflicts:0 numYields:1 nreturned:0 reslen:404 locks:{ Global: { acquireCount: { r: 6 } }, Database: { acquireCount: { r: 3 } }, oplog: { acquireCount: { r: 3 } } } protocol:op_command 5012ms

      Note that the message format is different for each type. I believe this has to be made consistent/unified as part of SERVER-17862. If this has been taken care of already, please feel free to close.

            Assignee:
            backlog-server-query Backlog - Query Team (Inactive)
            Reporter:
            dmitry.ryabtsev@mongodb.com Dmitry Ryabtsev
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: