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

AutoSplitVector should never choose null fields as split points

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • ALL
    • Sharding EMEA 2022-04-18
    • 136

    Description

      The AutoSplitVector command chooses split points by scanning the documents in a collection and choosing the new split point to be the shard key values of the first document that makes the chunk too large. If this document has any of the shard key values unset or set to null, this will result in the new chunk having a max key that doesn't have the right number of key values. We should modify the AutoSplitVector so that it never chooses null values as a split point.

      Attachments

        Activity

          People

            allison.easton@mongodb.com Allison Easton
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: