[SERVER-67246] Remove size multiple restriction on capped collections Created: 13/Jun/22  Updated: 29/Oct/23  Resolved: 08/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Leonardo Menti (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes SERVER-72063 Cannot create oplog with size of less... Closed
causes SERVER-74214 Cannot downgrade from fresh 6.2 due t... Closed
Related
is related to SERVER-67036 Creating capped collections does not ... Closed
is related to SERVER-74653 Remove CappedCollectionsRelaxedSize f... Closed
is related to SERVER-79590 [Storage Execution EMEA] Audit v7.0 f... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19
Participants:

 Description   

For historical reasons, the maximum size on capped collections are required to be a multiple of 256 bytes. This is most likely a limitation that made sense when we still supported the MMAP storage engine. We should look into removing this limitation.



 Comments   
Comment by Githook User [ 08/Sep/22 ]

Author:

{'name': 'Leonardo Menti', 'email': 'leonardo.menti@mongodb.com', 'username': 'leonardomenti'}

Message: SERVER-67246 Remove size multiple restriction on capped collections
Branch: master
https://github.com/mongodb/mongo/commit/22608cb9c7b2ce3771855dcb7d7fd6f564df4821

Comment by Benety Goh [ 13/Jun/22 ]

This ticket is a follow-up to SERVER-67036 but unlike SERVER-67036 is not required to be back ported to 6.0.

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