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

Add read/write concern fields to logging/profiling

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • None
    • Diagnostics
    • None
    • Minor Change
    • Sharding 2019-12-30

    Description

      Currently, logging/profiling includes read/write concern (RWC) by virtue of having been specified in the incoming command. However, when cluster-wide RWC defaults are applied to operations, they run with RWC other than the implicit server default, but appear in logs/profiling identically to operations that have not had any RWC applied (ie. have used the implicit server defaults). To avoid this misleading ambiguity, logging/profiling should include top-level readConcern and/or writeConcern fields when the RWC for the operation is something other than the implicit server default.

      Attachments

        Activity

          People

            kevin.pulo@mongodb.com Kevin Pulo
            kevin.pulo@mongodb.com Kevin Pulo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: