[DOCS-12970] Investigate changes in SERVER-42646: Cap splitVector response at max BSONObj size Created: 20/Aug/19  Updated: 13/Nov/23  Due: 12/Jun/20  Resolved: 09/Jun/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Andrew Feierabend (Inactive)
Resolution: Gone away Votes: 0
Labels: docs-onboarding-candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-42646 Cap splitVector response at max BSONO... Closed
Participants:
Days since reply: 4 years, 25 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work
Story Points: 0.5

 Description   

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.)


Generated at Thu Feb 08 08:06:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.