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

Do not omit the information about the batch if its too big

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Logging, Querying
    • ALL

      This is an example of line that we log for small (2 docs) batch inserts:

      2014-08-21T12:26:32.909-0400 [conn4] command test.$cmd command: insert { insert: "test", documents: 2, ordered: true } keyUpdates:0 numYields:0 locks(micros) w:292 reslen:40 285ms
      

      This is when the batch is big (10000 inserts):

      2014-08-21T12:29:39.264-0400 [conn5] command test.$cmd command: insert { $msg: "query not recording (too large)" } keyUpdates:0 numYields:0 locks(micros) w:345 reslen:40 128ms
      

      It's easy to see that the latter line is practically useless for diagnostic purposes as it has no information about the batch itself at all.

            Assignee:
            Unassigned Unassigned
            Reporter:
            alex.komyagin@mongodb.com Alexander Komyagin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: