-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Replication
We need a persistent way of keeping track of the mapping between donor optimes and recipient optimes in order to link together the recipient "no-op" entries for transactions and pre-images; this will be needed for change streams at least.
- is related to
-
SERVER-50936 Create a shutdown task that validates noops for tenant migrations
- Closed
- related to
-
SERVER-53510 Handle preImage and postImage for retryable writes
- Closed
-
SERVER-53573 Remove _opTimeMapping and tests making sure we chain no-ops correctly.
- Closed