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

Optimized path of shard collection fails to succeed with a large number of chunks

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.2.0, 5.0.5, 5.1.1
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v5.1, v5.0
    • Hide

      1. Run a shard collection with a hashed shard key and 8000 chunks

      Show
      1. Run a shard collection with a hashed shard key and 8000 chunks
    • Sharding EMEA 2021-11-01, Sharding EMEA 2021-11-15

    Description

      When sharding an empty collection, it is possible to pre-split the chunks across the cluster depending on the split policy initially associated with the collection. For example, if the shard key is hashed and an initial number of chunks is specified (using the numInitialChunks parameter) then the chunks will be equally distributed among the shards in the cluster automatically, given that the collection is empty.

      When committing the chunks to the config server, an upsert is used, this works fine for a small number of chunks (for example a thousand) but, with a large enough number, it is making one node on the config server to crash. The upsert operation could be replaced by an insert, but then the limitation will be the size of the BSONObj on the command.

      Attachments

        Issue Links

          Activity

            People

              marcos.grillo@mongodb.com Marcos José Grillo Ramirez
              marcos.grillo@mongodb.com Marcos José Grillo Ramirez
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: