Ensure Shard Merge supports large transactions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • 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

              Assignee:
              Christopher Caplinger
              Reporter:
              Christopher Caplinger
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: