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

Cap splitVector response at max BSONObj size

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • Sharding 2019-08-12, Sharding 2019-08-26

      The splitVector command will scan a chunk for shard key values to split a chunk at and return an array of chosen points. Currently it is possible for the size of the chosen points to make the response exceed the max BSONObj size limit of 16MB, leading splitVector to fail with BSONObjectTooLarge. When the shard key size limit is removed in SERVER-42368, this will become more likely, so splitVector should be modified to stop selecting split points when they would push the response over the BSON size limit and return the already chosen points. If possible, splitVector should return at least one split point.

            blake.oler@mongodb.com Blake Oler
            jack.mulrow@mongodb.com Jack Mulrow
            0 Vote for this issue
            6 Start watching this issue