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

Reshard Collection to the Same Shard Efficiency Improvement

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability

    Description

      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.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            matt.panton@mongodb.com Matt Panton
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: