On Jul 31, 12:03 pm, dormando <dorma...@rydia.net> wrote: > Yo, > > We've threatened to kill the `stats cachedump` command for probably five > years. I've daydreamed about randomizing the command name on every minor > release, every git push, ensuring that it stays around as a last ditch > debugging tool.
I remain a huge supporter of killing this. Thanks for starting this discussion. > - Streaming commands. > > Instead of (or as well as) running tcpdump tools, we could add commands > (or simply use TAP? I'm not sure if it overlaps fully for this) which lets > you either telnet in and start streaming some subset of information, or > run tools which act like varnishlog. Tools that can show the command, > the return value, and also the hidden headers. I owe all of you better tap documentation (the last couple of weeks have really killed me). It does some pretty great stuff in this area and has many practical uses. > - Commands to stream the keys of evictions, or also reclaims or expired > items > > People want cachedump so they can see what's still in there. This would be > an extension (or instead of) the previous streaming commands. You would > register for events with a set of flags, and when items expire or are > evicted or whatever you decided to watch, it would copy a result to the > stream. This fits into the current tap protocol as well. It's basically a protocol for anything where you want the server to come tell you stuff instead of you going to ask it.
