[SERVER-45623] RWC provenance Created: 17/Jan/20  Updated: 29/Oct/23  Resolved: 20/Feb/20

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

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

Issue Links:
Depends
Documented
is documented by DOCS-13433 Investigate changes in SERVER-45623: ... Closed
Related
is related to SERVER-45694 Larger RamLog maximum log line length... Backlog
is related to SERVER-45897 mongos should forward WriteConcernErr... Backlog
Backwards Compatibility: Minor Change
Sprint: Sharding 2020-01-27, Sharding 2020-02-10, Sharding 2020-02-24
Participants:

 Description   

Add and propagate provenance info to readConcern and writeConcern, to help with tracing where a given RWC has come from. This is especially useful when default RWC causes operations to fail (perhaps because the default RWC may be unsatisfiable).



 Comments   
Comment by Githook User [ 20/Feb/20 ]

Author:

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

Message: SERVER-45623 improve diagnosability of default writeConcern

Comment by Githook User [ 16/Feb/20 ]

Author:

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

Message: SERVER-45623 read/write concern provenance
Branch: master
https://github.com/mongodb/mongo/commit/95c8fc6a4a98f70b07f32565e3ef3e48172efa1e

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