Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-3035

Cache stuck full with 516 dirty leaf pages in single threaded test

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage 2016-12-12
    • None

      There was a Jenkins test failure with a timeout due to cache stuck full. The configured cache size is 32GB, and the configuration sets a single thread.

      Debug output:

      [1479850249:931660][18844:0x3fff9649f1b0], t, eviction-server: Cache stuck for too long, giving up: Connection timed out
==========
cache dump
file:wt(<live>): 
	internal: 1 pages, 0MB, 0/1 clean/dirty pages, 0/0 clean/dirty MB, 0MB max page, 0MB max dirty page
	leaf: 529 pages, 14MB, 13/516 clean/dirty pages, 0/14 clean/dirty MB, 1MB max page, 1MB max dirty page
file:WiredTiger.wt(<live>): 
	internal: 1 pages, 0MB, 0/1 clean/dirty pages, 0/0 clean/dirty MB, 0MB max page, 0MB max dirty page
	leaf: 1 pages, 0MB, 1/0 clean/dirty pages, 0/0 clean/dirty MB, 0MB max page, 0MB max dirty page
cache dump: total found = 16MB vs tracked inuse 16MB
total dirty bytes = 14MB
==========

      The original failure was: http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-ppc/8349/console

            Assignee:
            michael.cahill@mongodb.com Michael Cahill (Inactive)
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: