mongoimport ignores current nssize and requires db.repairDatabase() to be run.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 1.1.3
    • Component/s: Tools, Usability
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When doing and import with mongoimport using dbpath, ex:
      mongoimport -d Testing -c Joy --fields uid,name,activity --type csv --file /mnt/Testing.csv --dbpath /mnt/mdb/

      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.

            Assignee:
            Eliot Horowitz (Inactive)
            Reporter:
            Alexey Zilber
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: