-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
ALL
-
Execution Team 2022-03-21, Execution Team 2022-04-04
-
35
Generally, it is not correct to allow a transaction to commit with a commit timestamp at the stable timestamp, or a prepared transaction to commit with a durable timestamp at the stable timestamp. This can confuse checkpoint as to whether the newly committed transaction should be included in the checkpoint and can potentially lead to data inconsistencies.
With the merge of WT-7712, WiredTiger standalone builds fail attempts to set the commit or durable timestamps to the stable timestamp, but MDB Server builds are allowed to do so.
We do not know of any actual MDB Server problems in this area, but it would be good to fix any place where this happens and change the WiredTiger standalone behavior apply to all builds, to avoid the introduction of problems in the future.
- causes
-
SERVER-66139 Stuck on oplog visibility when inserting directly into oplog namespace in standalone mode
- Closed
- depends on
-
WT-7712 commit and durable timestamps should be disallowed at stable timestamp
- Closed
- is depended on by
-
WT-8902 MDB server sets the commit/durable timestamps equal to the stable timestamp
- Closed