[DOCS-4517] can we avoid the database disk size increases as a multiple of the CSV file in mongoimport? Created: 15/Dec/14 Updated: 03/Nov/17 Resolved: 15/Dec/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux Location: http://docs.mongodb.org/manual/faq/ |
||
| Participants: | |
| Days since reply: | 9 years, 9 weeks, 2 days ago |
| Description |
|
I am importing data from csv files of size more than 1GB (and have 15 files) using mongoimport. After importing near 20GB data it goes out of space on my system which has 250GB hard disk. I go through a post (Database size on disk increases as a multiple of the CSV file I mongoimport?) stating that mongodb increase the disk space in almost a factor of 10 times. Can we avoid this problem? or mongodb works in this way only. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 15/Dec/14 ] |
|
Please address issues like this to one of our support channels (e.g. http://www.mongodb.org/about/support). MongoDB's file allocation creates files for oplog (the local database,) and preallocates files to accommodate future growth, which sometimes leads to too much unused spaces, in cases where you're importing small or medium amounts of data into multiple databases. These characteristics are not unique to mongoimport or CSV files, but we would need to know more about the specifics of your workload to be able to draw any more specific conclusions about what's going on in your case. |