Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.2.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- neweng

Backwards Compatibility:
Fully Compatible
Backport Requested:

v6.0
Sprint:
Execution Team 2022-08-22, Execution Team 2022-09-05, Execution Team 2022-09-19
Linked BF Score:
0

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.

causes

SERVER-72063 Cannot create oplog with size of less than 10 bytes in standalone mode

Closed

SERVER-74214 Cannot downgrade from fresh 6.2 due to oplog cap size

Closed

SERVER-95549 Capped collection size is adjusted during rollback while FCV downgrading from 7.0 to 6.0

Closed

is related to

SERVER-67036 Creating capped collections does not use minimum size of 4096 bytes

Closed

SERVER-74653 Remove CappedCollectionsRelaxedSize feature flag after branching 7.0

Closed

SERVER-79590 [Storage Execution EMEA] Audit v7.0 feature flag

Closed

related to

SERVER-89877 `modify` change events don’t reflect effective cappedSize

Closed

(1 is related to, 1 related to)

Assignee:: Leonardo Menti (Inactive)

Reporter:: Benety Goh

Participants:: Benety Goh, Felipe Gasper, Githook User, Leonardo Menti

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: Jun 13 2022 08:28:40 PM UTC

Updated:: Oct 04 2024 09:38:02 PM UTC

Resolved:: Sep 08 2022 10:25:41 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates