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

Fassert due to WT_CACHE_FULL in failed index build cleanup on inMemory engine

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.3.10
    • Index Maintenance, Storage
    • None
    • Fully Compatible
    • ALL
    • 0

    Description

      In testing we have seen the following failure in the cleanup of a failed index build:

      [js_test:inmem_full] 2016-06-30T20:59:37.091+0000 d20510| 2016-06-30T20:59:37.090+0000 I INDEX    [conn1] build index on: test.large properties: { v: 1, key: { a: 1.0 }, name: "a_1", ns: "test.large" }
      [js_test:inmem_full] 2016-06-30T20:59:37.091+0000 d20510| 2016-06-30T20:59:37.090+0000 I INDEX    [conn1] 	 building index using bulk method
      [js_test:inmem_full] 2016-06-30T20:59:41.289+0000 d20510| 2016-06-30T20:59:41.289+0000 E INDEX    [conn1] Caught exception while cleaning up partially built indexes: -31807: WT_CACHE_FULL: operation would overflow cache
      [js_test:inmem_full] 2016-06-30T20:59:41.290+0000 d20510| 2016-06-30T20:59:41.289+0000 I -        [conn1] Fatal Assertion 18644
      [js_test:inmem_full] 2016-06-30T20:59:41.290+0000 d20510| 2016-06-30T20:59:41.289+0000 I -        [conn1]
      [js_test:inmem_full] 2016-06-30T20:59:41.290+0000 d20510|
      [js_test:inmem_full] 2016-06-30T20:59:41.290+0000 d20510| ***aborting after fassert() failure
      [js_test:inmem_full] 2016-06-30T20:59:41.291+0000 d20510|
      [js_test:inmem_full] 2016-06-30T20:59:41.291+0000 d20510|
      [js_test:inmem_full] 2016-06-30T20:59:41.297+0000 d20510| 2016-06-30T20:59:41.297+0000 F -        [conn1] Got signal: 6 (Aborted).
      

      I've tested attempting to reproduce and was unable to get the system to fail in this manner again.

      Looking at the code, I believe that we could handle this error case slightly better and retry the failed cleanup instead of just issuing an fassert.

      Attachments

        Issue Links

          Activity

            People

              david.hows David Hows
              david.hows David Hows
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: