[SERVER-72828] Ensure Shard Merge supports large transactions Created: 13/Jan/23  Updated: 27/Oct/23  Resolved: 10/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Christopher Caplinger Assignee: Christopher Caplinger
Resolution: Gone away Votes: 0
Labels: change-streams-support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-73053 after shard merge ops in change colle... Closed
Related
is related to SERVER-72354 Confirm that all change collection en... Closed
Participants:

 Description   

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



 Comments   
Comment by Christopher Caplinger [ 10/Apr/23 ]

Fixed by https://jira.mongodb.org/browse/SERVER-73053

Generated at Thu Feb 08 06:22:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.