You can not easily dump the cache. However, if you need, you can get a sense of what items are in there by using a combination of "stats items" and "stats cachedump" commands. This is a somewhat relevant thread:
http://groups.google.com/group/memcached/browse_thread/thread/632ce89cff47522d?pli=1 Regarding testing/troubleshooting: what are you trying to test/troubleshoot? Your app? Boris On Mon, Dec 29, 2008 at 2:45 PM, blazah <[email protected]> wrote: > > > Well, what would you do with the cache content dump if you had it? > > It doesn't sound like the problems in your app have anything to do > > with the content itself, but in how you're accessing the cache. > > Agreed -- this is most likely the case, which is why I doubt we'd ever > need to dump the cache contents. It is something that is desired, > however, so I'm trying to see how feasible a cache dump is to do. > > What other tests/diagnostics are typically run for memcached? I saw > that you developed a test suite using Python (http://github.com/dustin/ > memcached-test/tree/master<http://github.com/dustin/memcached-test/tree/master>) > -- Are there tests available that are > written in Java? Any other troubleshooting suggestions? > > Thanks -- > > -- --Boris
