[SERVER-12794] create command updates ns "size" option to actual min size Created: 19/Feb/14 Updated: 06/Dec/22 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Storage |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bernie Hackett | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
This may be intentional, based on some commits in https://github.com/mongodb/mongo/commit/6718e33f5ecd0de4a8550afaf789c2fc416b6eee MongoDB 2.4.9:
MongoDB 2.5.6-pre-
|
| Comments |
| Comment by Amalia Hawkins [ 18/Mar/14 ] | ||||||||||||||||
|
Our current behavior is to round the given capped collection size up to the nearest multiple of 256, then check if it's smaller than the minimum size (4096) – if it is smaller, then we use 4096 as the size instead. | ||||||||||||||||
| Comment by Githook User [ 21/Feb/14 ] | ||||||||||||||||
|
Author: {u'username': u'jmikola', u'name': u'Jeremy Mikola', u'email': u'jmikola@gmail.com'}Message: Fix createCollection tests for 2.5.x Use 4096 for capped collection size instead of 100, since server rounds up to the nearest extent anyway. As of https://jira.mongodb.org/browse/SERVER-12794, the actual storage size is reported, so we can use and expect 4096. Additionally, use dump_these_keys() to print collection options, so we don't need to worry about extra options or their order. | ||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 20/Feb/14 ] | ||||||||||||||||
|
test that fails on 2.4 but passes on 2.6
| ||||||||||||||||
| Comment by Daniel Pasette (Inactive) [ 19/Feb/14 ] | ||||||||||||||||
|
This has no impact on correctness. It is cosmetic, but leaving in rc1 to document. |