Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-16166

Investigate changes in SERVER-66208: Remove chunk creation for shard collection with existing data

    XMLWordPrintableJSON

Details

    Description

      Original Downstream Change Summary

      When sharding a non-empty collection, we only create one giant chunk on the db primary shard.
      Since we do not rely anymore on splitVector, sharding a collection is not subject anymore to the size limitation described in https://www.mongodb.com/docs/manual/reference/limits/#mongodb-limit-Sharding-Existing-Collection-Data-Size

      Description of Linked Ticket

      The UnoptimizedSplitPolicy for initial chunk creation chooses how many chunks to create using AutoSplitVector and creates all chunks on the primary shard. After disabling the autosplitter, it no longer makes sense to split the collection into chunks on a single shard for the initial split policy.

      After removing the autosplitter, we should just create a single chunk on the primary shard.

      Attachments

        Activity

          People

            joseph.dougherty@mongodb.com Joseph Dougherty
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              36 weeks, 3 days ago