Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-72828

Ensure Shard Merge supports large transactions

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 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

            Assignee:
            christopher.caplinger@mongodb.com Christopher Caplinger
            Reporter:
            christopher.caplinger@mongodb.com Christopher Caplinger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: