Reshard Collection to the Same Shard Efficiency Improvement

XMLWordPrintableJSON

    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Resharding a collection that is only located on one shard and has one chunk and is being resharded to only that shard (meaning the only shard it currently exists on) should be efficient as no data movement is required. We only have to do index creation (if the new shard key is not _id) and the metadata change commit.

      This will also be an optimization for unsharding a collection that only exists on one shard already as well.

              Assignee:
              [DO NOT USE] Backlog - Cluster Scalability
              Reporter:
              Matt Panton
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: