-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
There was a test failure in Jenkins test-format-stress-sanitizer overnight.
The failure was:
[1460587636:692581][82681:0x7f928edf4700], t, eviction-server: Cache stuck for too long, giving up: Connection timed out ========== cache dump file:wt.wt(<live>): internal pages: 1 pages, 1578 max, 0MB total leaf pages: 1 pages, 15466775 max, 14MB total file:WiredTigerLAS.wt(<live>): internal pages: 1 pages, 153 max, 0MB total file:WiredTiger.wt(<live>): internal pages: 1 pages, 4344 max, 0MB total dirty pages: 1 pages, 4344 max, 0MB total cache dump: total found = 15MB vs tracked inuse 15MB ==========
We have been seeing cache stuck error occasionally for a while, but this one is different. The cache is reasonably sized (15MB), and there is only a single leaf page. That indicates that we have failed to complete forced eviction on that page - since memory_page_max is 5MB in this case.
The original test results can be seen:
http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-sanitizer/9285
- is related to
-
WT-2565 item 3573 on page at [write-check] is a corrupted cell
- Closed
- links to