[SERVER-44538] Add read/write concern fields to logging/profiling Created: 11/Nov/19  Updated: 29/Oct/23  Resolved: 20/Dec/19

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: 4.3.3

Type: Improvement Priority: Major - P3
Reporter: Kevin Pulo Assignee: Kevin Pulo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Sprint: Sharding 2019-12-30
Participants:

 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.



 Comments   
Comment by Githook User [ 20/Dec/19 ]

Author:

{'name': 'Kevin Pulo', 'email': 'kevin.pulo@mongodb.com', 'username': 'devkev'}

Message: SERVER-44538 Add read/write concern fields to logging/profiling
Branch: master
https://github.com/mongodb/mongo/commit/8bf0a1988427e970c965994c629997a2a357dcd1

Generated at Thu Feb 08 05:06:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.