summaryrefslogtreecommitdiff
path: root/t/refhang.t
Commit message (Collapse)AuthorAgeFilesLines
* Find perl via /usr/bin/env instead of directlyDavid CARLIER2022-08-251-1/+1
| | | | | At least FreeBSD has perl in /usr/local/bin/perl and no symlink by default.
* disable refhang.t due to flakinessdormando2017-05-211-1/+5
| | | | test relies on jamming up network buffers, need better tooling.
* fix refhang test.dormando2015-01-081-27/+7
| | | | | | | | | The new code is a lot more efficient as unblocking LRU's as it's able to unlink refcounted items. However it's less aggressive in these cases. You'll get one OOM per stuck item and then it'll be gone in most cases. Removed the bottom half of the test since it's too flaky, and the above case now looks for both OOM's and STORED's plus relevant counters.
* rename reflocked + add protocol.txt linedormando2014-10-121-7/+7
| | | | | now lrutail_reflocked.. gross but more descriptive. will still make people thing something went wrong, oh well.
* Stats and tests for 'refhang' problemJay Grizzard2014-10-121-4/+39
| | | | | | | Add "reflocked" counter to "stats" and "stats items". Not sure if this is a good name for that or not. Add tests to verify a fully 'locked' LRU correctly reports oom
* Avoid OOM errors when locked items stuck in taildormando2014-10-121-0/+41
If a client fetches a few thousand keys, then does not ever read the socket, those keys will stay reflocked until the client disconnects or resumes. If some of those items are unpopular they can drop to the tail, causing all writes in the slab class to OOM. This creates some relief by chucking the items back to the head. Big thanks to Jay Grizzard and other folks at Box for helping narrow this down.