[SERVER-422] mongoimport ignores current nssize and requires db.repairDatabase() to be run. Created: 13/Nov/09 Updated: 10/Dec/14 Resolved: 18/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools, Usability |
| Affects Version/s: | 1.1.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alexey Zilber | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
When doing and import with mongoimport using dbpath, ex: The .ns file created will be 16M even though the config file and current setting is 2G for the ns file (our local config). The solution is to either add a -c option to mongoimport so it can read the config file settings or add the --nssize setting. Without this, after every import the db has to be repaired. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 18/Mar/14 ] |
|
The correct fix for this is |
| Comment by Eliot Horowitz (Inactive) [ 08/Dec/09 ] |
|
have you tested the performance of --dbpath with just running over tcp? |