[SERVER-20877] Under cache-full conditions serverStatus can become stuck Created: 12/Oct/15 Updated: 07/Dec/16 Resolved: 18/Nov/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, WiredTiger |
| Affects Version/s: | 3.0.6 |
| Fix Version/s: | 3.2.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Bruce Lucas (Inactive) | Assignee: | David Hows |
| Resolution: | Done | Votes: | 1 |
| Labels: | WTplaybook | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This is a spinoff from
This means that unfortunately no useful diagnostic data could be collected after the cache became full. Ideally serverStatus should succeed regardless of the state of the WT cache. |
| Comments |
| Comment by Githook User [ 19/Nov/15 ] | ||
|
Author: {u'username': u'daveh86', u'name': u'David Hows', u'email': u'howsdav@gmail.com'}Message: | ||
| Comment by Githook User [ 18/Nov/15 ] | ||
|
Author: {u'username': u'daveh86', u'name': u'David Hows', u'email': u'howsdav@gmail.com'}Message: | ||
| Comment by David Hows [ 04/Nov/15 ] | ||
|
On re-run
I have another patch for this in CR: With a re-run and rebase I get immediate returns. | ||
| Comment by Alexander Gorrod [ 03/Nov/15 ] | ||
|
david.hows Could you re-run your reproducer with a debug build including the latest WiredTiger drop. I'm interested to see whether it times out after 5 minutes due to the new diagnostic code added here: https://github.com/wiredtiger/wiredtiger/commit/66b44e1344219f445305248cb1ea630536af41d2 |