Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
We document here that sharded transactions are not allowed with writeConcernMajorityJournalDefault:false. I think it's also important to specify that regardless of the user's requested writeConcern, commitTransaction for a sharded transaction must perform some component writes with writeConcern {w: "majority", j: true. If we don't specify this, users may be confused as to why running commitTransaction with a weaker writeConcern doesn't significantly speed up their sharded transactions.
(Additionally, until SERVER-37364 is complete, there is no behavior difference for weaker writeConcerns, but I don't think we need to document this.)
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- is related to
-
SERVER-44638 j:false is ignored in startTransaction write concern
-
- Closed
-
-
SERVER-37364 Coordinator should return the decision to the client as soon as the decision is durable
-
- Closed
-