-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.7.1
-
Component/s: Performance, Storage
-
None
-
ALL
-
The documentation for db.createCollection states the following for the size parameter:
If capped is false, you can use this field to preallocate space for an ordinary collection.
This was true prior to r2.7.1 but the size parameter gets silently ignored in HEAD when the collection to be created is not capped. It was the only (documented) way not to allocate a lot of extents for a collection that was supposed to grow to a large size, say 500 MiB.
I have a patch to resurrect this feature. I'll send a pull request after submitting this issue.
- duplicates
-
SERVER-13144 Size value is ignored when creating non-capped collections
- Closed
- links to