-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Repl 2021-03-08, Repl 2021-03-22
-
178
As part of writing noop oplog entries on the recipient, use TransactionParticipant (and config.transactions) itself to cache the OpTime of the last noop oplog entry for each session to create an oplog chain for retryable writes and update config.transactions.
The noop oplog entry should contain "fromMigrate: true" and contain the original oplog entry in the "o2" field so that the SessionUpdateTracker on secondaries recognizes the noop oplog entry as a retryable write oplog entry and updates its config.transactions.
- depends on
-
SERVER-53319 Fetching retryable writes from before startFetchingOpTime
- Closed
- is depended on by
-
SERVER-53510 Handle preImage and postImage for retryable writes
- Closed
- is related to
-
SERVER-53946 Resume batching from the last noop entry even if it is less than the startApplyingDonorOpTime
- Closed