[DOCS-5931] Confusing preallocDataFiles description Created: 30/Jul/15 Updated: 30/Oct/23 Resolved: 14/Nov/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 5 years, 13 weeks ago | ||||||||
| Description |
|
http://docs.mongodb.org/manual/reference/configuration-options/#storage.mmapv1.preallocDataFiles
What does this actually mean? I presume from the earlier "Default: True" line that "enabled" is the default? If so, this is actually not necessarily the case in current versions. It also feels like it clashes with the deprecated status and the statement "Exists for future compatibility and clarity." (should that be "backwards compatibility"?) As well as fixing the language, this should describe the current behaviour with respect to data file preallocation. |
| Comments |
| Comment by Githook User [ 14/Nov/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 14/Nov/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 14/Nov/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |
| Comment by Githook User [ 14/Nov/18 ] |
|
Author: {'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |