[SERVER-42646] Cap splitVector response at max BSONObj size Created: 06/Aug/19  Updated: 29/Oct/23  Resolved: 20/Aug/19

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Blake Oler
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-12970 Investigate changes in SERVER-42646: ... Closed
Related
is related to SERVER-34877 findAndModify with upsert allows crea... Closed
is related to SERVER-42368 Remove max shard key value size limit Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-08-12, Sharding 2019-08-26
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 20/Aug/19 ]

Author:

{'name': 'Blake Oler', 'email': 'blake.oler@mongodb.com', 'username': 'BlakeIsBlake'}

Message: SERVER-42646 Cap splitVector response at max BSONObj size
Branch: master
https://github.com/mongodb/mongo/commit/73567b08e52e490d2e47603796fde950f9032eab

Generated at Thu Feb 08 05:01:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.