Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-3932

WiredTiger memory allocation failure in js_test

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.6.4, 3.7.3, WT3.1.0
    • None
    • None

    Description

      Some test cases (e.g. aggregation, gle_auth) of a recent evergreen patch build failed regarding WiredTiger memory allocation failure. Please note mmapv1 configuration was detected at the beginning of those tests.

      [js_test:testshard1] 2018-02-21T23:43:06.871+0000 d20510| 2018-02-21T23:43:06.871+0000 W STORAGE  [initandlisten] Detected configuration for non-active storage engine mmapv1 when current storage engine is wiredTiger
      ...
      [js_test:testshard1] 2018-02-21T23:43:11.358+0000 c20513| 2018-02-21T23:43:11.357+0000 E STORAGE  [initandlisten] WiredTiger error (12) [1519256591:357915][11400:0x7ffd01700a60], wiredtiger_open: memory allocation of 348842480 bytes failed: Cannot allocate memory
      [js_test:testshard1] 2018-02-21T23:43:11.360+0000 c20513| 2018-02-21T23:43:11.360+0000 E -        [initandlisten] Assertion: Location28595: 12: Cannot allocate memory src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 422
      [js_test:testshard1] 2018-02-21T23:43:11.370+0000 c20513| 2018-02-21T23:43:11.370+0000 I STORAGE  [initandlisten] exception in initAndListen: Location28595: 12: Cannot allocate memory, terminating
      

      Attachments

        Activity

          People

            michael.cahill@mongodb.com Michael Cahill
            luke.chen@mongodb.com Luke Chen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: