-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2019-02-25, Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08
-
10
We will no longer pin the stable timestamp behind the oldest prepare timestamp, or behind the oldest prepare timestamp of a transaction whose corresponding commit/abort oplog entries have not been majority committed. That is, we will revert SERVER-35811.
- depends on
-
WT-4607 Allow prepared transaction to commit behind oldest timestamp
- Closed
-
SERVER-39035 Specify durable_timestamp when committing prepared transaction
- Closed
-
SERVER-40008 Storage Interface changes to specify rounding off for prepare and commit timestamps.
- Closed
- is depended on by
-
SERVER-37886 Remove config server as coordinator crutch from coordinator stepdown targeted tests
- Closed
-
SERVER-39038 Remove the restriction that the ‘oldest_active_txn_timestamp’ is greater than the initial data timestamp before exiting ‘STARTUP2’
- Closed
-
SERVER-39039 Persist commit decision with writeConcern w:majority
- Closed
-
SERVER-39040 Coordinator should send prepareTransaction with w:majority
- Closed
-
SERVER-39510 Test that transaction coordinator going down does not lead to catastrophic failure
- Closed
-
SERVER-39991 Add transactions workloads to failover concurrency suites
- Closed
-
SERVER-40268 Add a test that should test reconstruct prepared transaction oplog entry during recovery(startup/rollback).
- Closed