On Dec 29, 3:11 pm, "Boris Partensky" <[email protected]> wrote: > 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/632ce89... > > Regarding testing/troubleshooting: what are you trying to test/troubleshoot? > Your app?
We have three separate applications accessing our memcached servers; 2 are UI based, 1 is not. We use a single memcached instance for all cached information and have 20 server IP addresses configured on 2 machines. We have multiple schedulers running which retrieve objects from the cache. We often run into problems when more than 2 schedulers are turned on with memcached enabled. I'm still trying to understand what's happening by going through the logs, but it would be helpful to be able to perform a set of tests. Ideally, we'd like to develop memcached tools to do the following: o Check the status of memcached servers and print server stats on demand (this appears doable based on various posts) o Do more network and client configuration testing -- scenarios such as memcached servers going down and optimizing the client configuration (this may also be easier if we investigate using Dustin's improved Java client library vs the Java 2.0.1 client -- thanks Dustin for the information) I appreciate everyone's suggestions and help. I'm going to change the number of server IPs from 20 to 2 (one IP address per server) and see how the schedulers run. We see very little load on the memcached servers so I doubt whether this is going to fix the issue of our schedulers getting stuck when memcached is enabled. I need to investigate this further since I don't fully understand what's going on yet.
