dumb hack to self-repair stuck slabs

since 1.2.6, most of the refcount leaks have been quashed.
I still get them in production, extremely rarely.
It's possibly we'll have refcount leaks on and off even in the future.

This hack acknowledges this and exists since we want to guarantee, as much as
possible, that memcached is a stable service. Having to monitor for and
restart the service on account of "rare bugs" isn't acceptable.

1 files changed, 3 insertions, 0 deletions

diff --git a/doc/protocol.txt b/doc/protocol.txt
index 6dd4cf6..6ce04eb 100644
--- a/doc/protocol.txt
+++ b/doc/protocol.txt
@@ -478,6 +478,9 @@ evicted_time           Seconds since the last access for the most recent item
 outofmemory            Number of times the underlying slab class was unable to
                        store a new item. This means you are running with -M or
                        an eviction failed.
+tailrepairs            Number of times we self-healed a slab with a refcount
+                       leak. If this counter is increasing a lot, please
+                       report your situation to the developers.
 
 Note this will only display information about slabs which exist, so an empty
 cache will return an empty set.