index restore/creation causes 'out of memory' & process termination

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.0.1
    • Component/s: Index Maintenance
    • None
    • Environment:
      Xen 4.2.5-34.el6 host
      Ubuntu Server 14.04 x64
      1GB RAM, 2CPU
    • Linux
    • Hide

      mongorestore -v -j 1 --stopOnError --dir ~/mongodb_backup_301/coinb/trades.bson -d coinb -c trades

      works though when specifying --noIndexRestore, but fails when using createIndex to re-implement indexing afterwards

      index specified: {"v":1,"unique":true,"key":

      {"exchange":1,"tid":1}

      ,"name":"exchange_1_tid_1","ns":"coinb.trades"}
      (exchange is a short string, tid is a number)

      Show
      mongorestore -v -j 1 --stopOnError --dir ~/mongodb_backup_301/coinb/trades.bson -d coinb -c trades works though when specifying --noIndexRestore, but fails when using createIndex to re-implement indexing afterwards index specified: {"v":1,"unique":true,"key": {"exchange":1,"tid":1} ,"name":"exchange_1_tid_1","ns":"coinb.trades"} (exchange is a short string, tid is a number)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      using WT, when index is created from either a) mongorestore or b) createIndex, this causes an 'out of memory' error and terminates the mongod process.

      > db.trades.stats()

      { "ns" : "coinb.trades", "count" : 23017771, "size" : 36313819242, "avgObjSize" : 1577, "storageSize" : 914694144, "capped" : false }

        1. console.out
          8 kB
        2. mongod.conf
          0.3 kB
        3. mongodb.log
          11 kB

            Assignee:
            Ramon Fernandez Marina
            Reporter:
            Warwick Brown
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: