Renaming a sharded collection can hit transaction limit

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We use transaction to make changes on the config metadata when performing rename. However, the size of the transaction is also a function of the number of tags/zones of the collection being renamed.

      Resharding also has a similar problem when it tries to swap out the original sharded collection with the new collection with the new shard key as it also uses transactions to perform the rename.

              Assignee:
              Unassigned
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: