-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
Sharding 2018-07-30, Sharding 2018-08-13
If the first statement in a transaction does not specify snapshot readConcern, mongod will implicitly upconvert it to snapshot. Mongos currently does not have this behavior, and because many core/txns tests rely on this, either mongos will need to upconvert readConcerns to snapshot as well (until we support transactions with other readConcern levels) or the tests need to be updated to explicitly choose snapshot readConcern.
- is related to
-
SERVER-35709 mongos should remember readConcern setting for multi statement transaction
- Closed