Hi Pramod, First of all the version of memcached you're using is old. Upgrade. The latest version is 1.4.5 with another release being imminent from what I hear. Available from here: http://memcached.org/
You can take a look at this Perl script. It's a handy way to dump the contents of your memcached instance for further examination. Just don't do it in production. https://github.com/mmucklo/memcached/blob/master/scripts/memcached-tool Also, take a look at mk-query-digest from Maatkit. It has the ability to run a report against memcached traffic captured using tcpdump as follows showing histograms of popular keys, sizes etc. So assuming you're using the default port for memcached (11211) run: sudo tcpdump -s 65535 -x -n -q -tttt -i eth0 port 11211 > memc_tcpdump.txt mk-query-digest --type memcached memc_tcpdump.txt HTH Thanks, Paul On Tue, Jun 7, 2011 at 2:18 PM, Pramod Sadalage <[email protected]>wrote: > Paul, > > we are using 1.4.1 with default configuration. the calling tech stack is > Java. > > Thanks > *Pramod Sadalage > @pramodsadalage > <http://www.twitter.com/pramodsadalage><http://www.sadalage.com/> > * > *www.sadalage.com > www.databaserefactoring.com* > > > > On Tue, Jun 7, 2011 at 9:40 AM, Paul Gale <[email protected]> wrote: > >> What version of memcached are you using? >> What command line parameters are you passing to memcached etc? >> Just out of curiosity, what is the calling client technology stack in use >> here? >> >> Thanks, >> Paul >> >> >> On Tue, Jun 7, 2011 at 10:06 AM, Pramod Sadalage < >> [email protected]> wrote: >> >>> Hello, >>> >>> We see errors in MemCached as shown below with "error storing data in >>> cache for key". >>> >>> com.danga.MemCached.MemCachedClient Tue Jun 07 08:49:57 CDT 2011 - +++ >>> + error storing data in cache for key: length: 2392 >>> >>> I was wondering what is the "2392", bytes over the limit allowed by >>> memcached? or total size of the object in kb, bytes etc? >>> >>> Thanks >>> Pramod >> >> >> >
