Batch the transactions in the commit of movePrimary

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When featureFlagTrackUnshardedCollectionsOnShardingCatalog is enabled, the commit of movePrimary on the config server needs to update the chunk entry for each unsharded collection that is located on the prior dbPrimary. If there are many collections in the database, this could make the transaction exceed the size limit for transactions.

      We should split this transaction into batches so that we are sure we won't exceed the max transaction size.

              Assignee:
              [DO NOT USE] Backlog - Catalog and Routing
              Reporter:
              Allison Easton
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: