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

Renaming a sharded collection can hit transaction limit

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

      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:
            backlog-server-catalog-and-routing Backlog - Catalog and Routing
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: