[SERVER-16697] MongoDb terminate when WT fault STATUS_STACK_OVERFLOW Created: 30/Dec/14  Updated: 03/Feb/15  Resolved: 20/Jan/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.8.0-rc4
Fix Version/s: 3.0.0-rc6

Type: Bug Priority: Major - P3
Reporter: Eitan Klein Assignee: Keith Bostic (Inactive)
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stackFrame-ff.txt    
Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

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

Participants:

 Description   

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);
   }



 Comments   
Comment by Daniel Pasette (Inactive) [ 02/Jan/15 ]

I ran this workload several several times on Linux without problem. The workload is very simple, but maybe a windows only issue?

Generated at Thu Feb 08 03:41:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.