[SERVER-61011] Evaluate RecordId size limit for clustered collections Created: 26/Oct/21  Updated: 29/Oct/23  Resolved: 14/Jan/22

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

Type: Task Priority: Major - P3
Reporter: Haley Connelly Assignee: Daniel Gomez Ferro
Resolution: Fixed Votes: 0
Labels: PM-2311-M2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-12-13, Execution Team 2021-12-27, Execution Team 2022-01-10, Execution Team 2022-01-24
Participants:
Linked BF Score: 60

 Description   

Right now, it is arbitrary. The cluster key, which is also encoded in the RecordId for a document in a clustered collection, is currently capped at 4MB. Since the BSONSizeLimit is 16MB, we should explore supporting larger RecordId sizes.



 Comments   
Comment by Githook User [ 14/Jan/22 ]

Author:

{'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}

Message: SERVER-61011 Serialize RecordId to BinData and increase size limit to 8MB
Branch: master
https://github.com/mongodb/mongo/commit/e31937600f401cea1231b37bc3eacc379b2df546

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