MongoDB's replication rollback can discard recent history back to the majority commit timestamp. If we allow WiredTiger's oldest_timestamp to move past the commit point, we need a way to move it backwards during rollback. MongoDB's replication layer takes care of correctness of timestamp reads in this case.
- is depended on by
-
SERVER-32022 allow enableMajorityReadConcern=false to work
- Closed
- links to