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

MongoDb terminate when WT fault STATUS_STACK_OVERFLOW

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.0.0-rc6
    • Affects Version/s: 2.8.0-rc4
    • Component/s: Storage
    • Labels:
    • Fully Compatible
    • ALL
    • Hide

      Test environment

      1) 2 replica set on windows
      2) Hammar.mango with insert profile

      go run hammer.mongo.go -server=10.4.101.199:27017 -profile=INSERT -worker=90 -totaltime=30000

      Show
      Test environment 1) 2 replica set on windows 2) Hammar.mango with insert profile go run hammer.mongo.go -server=10.4.101.199:27017 -profile=INSERT -worker=90 -totaltime=30000

      On insert only stress scenario when I limit the cache_size = 1G, I observed terminate of mongodb.exe with the text below (no full stack).

      10.4.111.166:52194 #1259 (1 connection now open)



      10.4.111.166:52194 #1259 (1 connection now open)
      2014-12-29T20:01:12.713-0800 I CONTROL *** unhandled exception 0xC00000FD at 0x
      00007FF7A1465302, terminating
      2014-12-29T20:01:12.714-0800 I CONTROL *** stack trace for unhandled exception:

      The list nearest symbols for 0x00007FF7A1465302 pointing to the location below, c:\data\mci\shell\src\src\third_party\wiredtiger\src\evict\evict_page.c(310)+0x2
      I assume this happened because of the recursion below

      /*
         * Recurse through the page's subtree: this happens first because we
         * have to write pages in depth-first order, otherwise we'll dirty
         * pages after we've written them.
         */
         if (WT_PAGE_IS_INTERNAL(page)) {
                WT_WITH_PAGE_INDEX(session, ret = __evict_review_subtree(
                    session, ref, exclusive, inmem_splitp, istreep));
                WT_RET(ret);
         }
      

            Assignee:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Reporter:
            eitan.klein Eitan Klein
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: