-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
Repl 2018-11-19, Repl 2019-02-11, Repl 2019-02-25, Repl 2019-03-11, Repl 2019-03-25, Service Arch 2019-04-22, Repl 2019-04-08
-
0
- depends on
-
SERVER-36811 Provide a mechanism for replication to specify the 'maximum_truncation_timestamp' for a given 'stable_timestamp'
- Closed
-
SERVER-39679 Add callback to replication when storage takes a checkpoint to learn of the maximum oplog truncation timestamp
- Closed
- is depended on by
-
SERVER-40457 test that secondaries roll over their oplogs when they exceed oplogSize
- Closed
- related to
-
SERVER-39627 Audit uses of TransactionParticipant::SideTransactionBlock
- Closed
-
SERVER-36772 Ensure oplog cannot be truncated due to capped deletions in standalone mode
- Closed
-
SERVER-38165 Test that prepared transactions work with an in-memory secondary
- Closed
-
SERVER-39680 Maintain the oldest active transaction timestamp only with the transaction table
- Closed
-
SERVER-39989 Use a config.transactions find command for the begin fetching timestamp in initial sync
- Closed
-
SERVER-30460 Grow the oplog when the replication commit point falls behind the back of where it would normally be truncated to
- Closed