We want the ability to be able to dump the cache in case there is a "problem". The likelihood of us dumping the cache is slim but we want to be able to do this in the future so we can capture what was in the cache at the time of failure. I believe the real issue is our configuration in production. I'd like to develop or utilize tests that help to diagnose configuration/threading issues. What do people use for troubleshooting purposes?
The problem that we're seeing in production seems to be related to threads since our schedulers get stuck when memcached is turned on and the application is fine when memcached is turned off. I'm still looking into the problems that we've been seeing so my apologies for not being able to be more specific. On Dec 29, 12:03 pm, Dustin <[email protected]> wrote: > On Dec 29, 8:30 am, blazah <[email protected]> wrote: > > > Hi, > > I realize that one shouldn't iterate through the contents of the > > memcached server, but in the case of testing/verification, I want to > > be able to dump the cache, if necessary. I did see the FAQ post and > > understand this shouldn't be done in production. > > > I know the Java client API doesn't support getting the contents of the > > cache and iterating through it's values. Can someone recommend a way > > to do this or other effective ways to test memcached? > > What are you trying to test? > > I think I'd need a bit more input from you before we could converge > on effective testing, as I can't imagine what test I'd be conducting > that would benefit from the contents of memcached being dumped.
