Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Minor Change
-
Sharding 2020-01-27, Sharding 2020-02-10, Sharding 2020-02-24
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).
Attachments
Issue Links
- is documented by
-
DOCS-13433 Investigate changes in SERVER-45623: RWC provenance
-
- Closed
-
- is related to
-
SERVER-45694 Larger RamLog maximum log line length when testing
-
- Backlog
-
-
SERVER-45897 mongos should forward WriteConcernError errInfo from shards
-
- Backlog
-