-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Index Maintenance, Storage
-
None
-
Fully Compatible
-
ALL
-
0
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
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.
- is related to
-
SERVER-26239 Improve handling of WT_CACHE_FULL for inMemory storage engine
-
- Closed
-