-
Type: Bug
-
Resolution: Fixed
-
Priority: Blocker - P1
-
Affects Version/s: None
-
Component/s: None
Currently the prepare timestamp is checked for being >= oldest (and rounded up if necessary and thus configured) – this check should be against stable, since otherwise it's possible to commit before stable and that leads to data inconsistency.
- depends on
-
SERVER-63166 Restrict prepare_timestamp to be > stable, not >= oldest
- Closed
- is related to
-
WT-8747 Reading between commit_timestamp and durable_timestamp can produce inconsistency
- Closed
-
SERVER-60037 Enable the ordered timestamp assertion in MongoDB
- Closed