-
Type: Task
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
Currently, we are unable to resume a change stream on the recipient after a large (>16mb) transaction is committed on the Donor. When attempting to resume the change stream on the Recipient, we get a ChangeStreamHistoryLost error. We should ensure that this works properly for transactions committed before the migration, and those committed during oplog catchup.
Also, we'll want to remove tenant_migration_recipient_shard_merge_copies_change_collections.js from the the exclude_files list in replica_sets_large_txns_format.yml
- depends on
-
SERVER-73053 after shard merge ops in change collection have no coresponding entry in oplog
- Closed
- is related to
-
SERVER-72354 Confirm that all change collection entries are handled for shard merge
- Closed