Details
-
Task
-
Resolution: Done
-
Critical - P2
-
None
-
None
-
None
-
None
Description
After some discussion, we've decided to make readConcern: Majority's behavior be undefined when using protocolVersion 0. At some point in the future we will explicitly have readConcern:Majority reads throw errors when using Protocol Version 0, but for now the behaviour is undefined and provides no guarantees.
We should recommend always using ProtocolVersion 1 when using readConcerns: Majorioty.
Can we make sure this gets reflected in the docs?
Attachments
Issue Links
- is related to
-
DOCS-6624 3.2 readConcern
-
- Closed
-