-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08
Currently, when we commit a prepared transaction as a part of commit oplog replay, we don't set any timestamp (commit & durable timestamp) to the wiredTiger transaction via recovery unit. So, basically we are committing the write operations as non-timestamped. This would cause problem for data visibility and durability.
- depends on
-
WT-4607 Allow prepared transaction to commit behind oldest timestamp
- Closed
-
SERVER-40008 Storage Interface changes to specify rounding off for prepare and commit timestamps.
- Closed
-
WT-4621 Support rounding up prepare timestamp to oldest
- Closed
- related to
-
SERVER-39035 Specify durable_timestamp when committing prepared transaction
- Closed