Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-16311

WiredTiger: lsm-worker: LSM metadata write: Cannot allocate memory

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Hide

      Start server

      mongod --storageEngine wiredtiger --wiredTigerCollectionConfig "type=lsm" --wiredTigerIndexConfig "type=lsm" --logpath mongod-wt-lsm-2.log

      Create an index

      db.tstest.ensureIndex( { device_id : 1, ts : 1 } )

      git clone https://github.com/henrikingo/mongo-timeseries-benchmark.git
cd mongo-timeseries-benchmark
python timeSeriesTest.py

      After 2k to 5k iterations, mongod will assert with the shown error.

      If it matters, I was running this in AWS on a cc2.8xlarge instance with the mongodb database on a single local/ephemeral disk.

      Show
      Start server mongod --storageEngine wiredtiger --wiredTigerCollectionConfig "type=lsm" --wiredTigerIndexConfig "type=lsm" --logpath mongod-wt-lsm-2.log Create an index db.tstest.ensureIndex( { device_id : 1, ts : 1 } ) git clone https: //github.com/henrikingo/mongo-timeseries-benchmark.git cd mongo-timeseries-benchmark python timeSeriesTest.py After 2k to 5k iterations, mongod will assert with the shown error. If it matters, I was running this in AWS on a cc2.8xlarge instance with the mongodb database on a single local/ephemeral disk.

      I'm starting mongodb in WiredTiger type=lsm mode (both indexes and collections). After inserting between 200M to 500M rows, mongod crashes with " lsm-worker: LSM metadata write: Cannot allocate memory".

      The test was run in a very IO constrained HW setup.

        1. mongod-wt-lsm-2.log
          3.74 MB

            Assignee:
            henrik.ingo@mongodb.com Henrik Ingo (Inactive)
            Reporter:
            henrik.ingo@mongodb.com Henrik Ingo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: