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

Add read/write concern fields to logging/profiling

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 4.3 Required
    • Component/s: Diagnostics
    • Labels:
      None

      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

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: