[SERVER-16800] Conflict between documentation of storage.quota.enforced and code Created: 11/Jan/15 Updated: 11/Jan/15 Resolved: 11/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.6.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Cailin Nelson | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
storage.quota.enforced is documented in the 2.6. Configuration File Options docs: http://docs.mongodb.org/manual/reference/configuration-options/#storage.quota.enforced I believe this implies that I should be able to use this option in a YAML config file. However, the code defines this as a legacy-only option: https://github.com/mongodb/mongo/blob/v2.6/src/mongo/db/mongod_options.cpp#L196 Not sure who is correct, please just move this to DOCS if its just a documentation blooper. |
| Comments |
| Comment by Cailin Nelson [ 11/Jan/15 ] |
|
Thanks, Adam. I'll leave a comment over on the original report. |
| Comment by Adam Midvidy [ 11/Jan/15 ] |
|
This was fixed on master in |