-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2018-12-03, Repl 2018-12-17, Repl 2019-01-14, Repl 2019-01-28
Transactions that touch a single shard that contains an arbiter or contains a node with enableMajorityReadConcern:false will be allowed in 4.2. We should test that:
- A single shard transaction can succeed against a replica set that contains an arbiter.
- A single shard transaction can succeed against a replica set whose primary has enableMajorityReadConcern:false and whose secondary is lagged. We should test this to make sure that the transaction is selecting a read timestamp based on lastApplied, as opposed to starting at the majority commit point. If it started at the majority commit point, we would not be able to obtain a snapshot, since we won't keep history back that far.
- depends on
-
SERVER-37897 Disable table logging for data files when enableMajorityReadConcern=false
- Closed
- related to
-
SERVER-37549 Compute atClusterTime for sharded transactions using lastApplied opTime timestamps of targeted shards
- Closed