Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.3.4
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Minor Change
Sprint:
Sharding 2020-01-27, Sharding 2020-02-10, Sharding 2020-02-24
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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).

is related to

SERVER-45694 Larger RamLog maximum log line length when testing

Backlog

SERVER-45897 mongos should forward WriteConcernError errInfo from shards

Backlog

Assignee:: Kevin Pulo
Reporter:: Kevin Pulo
Participants:: Githook User, Kevin Pulo
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Jan 17 2020 02:56:21 AM UTC
Updated:: Oct 29 2023 10:13:10 PM UTC
Resolved:: Feb 20 2020 05:53:58 AM UTC
Confidence Status Last Update:: 16/Feb/20 5:39 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates