[SERVER-8895] Writes fail when new files cannot be preallocated even in the existing data file has space Created: 07/Mar/13 Updated: 08/Mar/13 Resolved: 07/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Dharshan Rangegowda | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
I have a Mongo machine with about 1GB of disk space for mongo data but I am only able to use about 250 MB of it. The stats are below. Looks like the data files are preallocated to about 1GB - shouldn't I be able to use the entire preallocated 1GB allocated instead of just 250 MB? Writes are failing due to lack of disk space. { Here is the error that I see in the log file |
| Comments |
| Comment by Dharshan Rangegowda [ 07/Mar/13 ] |
|
I've heard the noprealloc option has a performance impact and is not suggested for production databases. Is there a rule of thumb I can use to estimate how much prealloc space I need to get x amount of mongo data? E.g. If I want to get to 1GB of MongoDB data with small files how much realistic data space do I need? |
| Comment by Scott Hernandez (Inactive) [ 07/Mar/13 ] |
|
You can use the noprealloc option when starting the server: http://docs.mongodb.org/manual/reference/configuration-options/#noprealloc You may also be interested in the smallfiles option as well. |