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

Investigate changes in SERVER-42646: Cap splitVector response at max BSONObj size

      Description

      Downstream Change Summary

      The splitVector command (which is used when splitting a chunk) will now stop selecting split points when the number of split points has reached the maximum BSONObj size limit. Previously, it was possible for the size of the chosen points to exceed said limit, and then the splitVector command would fail with BSONObjectTooLarge.

      Description of Linked Ticket

      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.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            andrew.feierabend@mongodb.com Andrew Feierabend (Inactive)
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              4 years, 40 weeks, 2 days ago