doubt while memcached
Hi, Please let me know, how objects are chached, while doing memcache in different memcache server.. Thanks in advance. Regards N.SenthilRaja. -- To unsubscribe, reply using remove me as the subject.
Re: doubt while memcached
On Wed, Apr 14, 2010 at 09:47, Senthil Raja nsenthilraj...@gmail.com wrote: Hi, Please let me know, how objects are chached, while doing memcache in different memcache server.. That depends on your memcache client, not on memcache server, and many implement several sharding algorithms. The best ones are those that offer consistent hashing, which allows you to add / remove servers from the list without flushing the full dataset, just only the corresponding % of change. -- Guille -ℬḭṩḩø- bishi...@gmail.com :wq -- To unsubscribe, reply using remove me as the subject.
MemCache failure: undefined class/module 'modelname' (Rails 2.0.2, gem memcache-client 1.8.2, Debian Lenny memcached 1.2.2)
Hy, my memcached show curious behaviour. First, some arrays contain model objects which i set with CACHE.set(key, value) are cached ok but when i want to get back this value in another action in the same controller i get a nil object. The myterie is that i get the correct object array back when i type the code puts CACHE.get(key) in the irb console of my project Another Problem is almost the same. Cache object array is ok but the irb console get MemCache failure: undefined class/module 'modelname' The mystery in this case is that this worked yesterday. I think this is a bug but i cannot resolve it. Can somebody help me? subsonnic -- To unsubscribe, reply using remove me as the subject.
Re: sporadic high max response times and client timeout strategies
How did you notice the swapping? I struggled with a similar issue, we finally disabled one of our monitoring tools (hyperic hq) which solved the problem. But we didn't find out why/how the monitoring tool caused the issue. Anything you find out would be helpful. Peter On Mon, Apr 12, 2010 at 1:52 AM, Ryan Tomayko rtoma...@gmail.com wrote: On Wed, Apr 7, 2010 at 3:02 AM, Ryan Tomayko rtoma...@gmail.com wrote: On Wed, Apr 7, 2010 at 2:14 AM, dormando dorma...@rydia.net wrote: Just about all respones should happen sub-ms (excepting for network jitter). Thanks for the quick response. Some stuff you can check for offhand: - List versions of all related software you're running; memcached proper, libmemcached, ruby client) memcached 1.4.0 amd64 built from custom debian package memcached ruby lib is 0.17.3 (bundles libmemcached 0.32) I used the memslap from libmemcached 0.38 in my benchmarks - Your full startup arguments to memcached /usr/bin/memcached -d -m 12288 -c 200 -l 172.17.0.139 -p 11211 -U 11211 -P /var/run/memcached.pid -u nobody - Narrow down if these timeouts happen if it's initiating a new connection to memcached, or when reusing a persistent connection, or both (may not be easy). Hmm. I'll need to give this some thought. Let me tackle this tomorrow. - If your memcached is (hopefully) new enough, is 'listen_disabled_num' under the `stats` command nonzero? If so, you're hitting maxconns and memcached is blocking new connections until old ones disconnect. Seems unlikely for your case. Yep. I checked listen_disabled_num during my tests and frequently in the past because -c 200 always seemed low to me. I've never seen it at anything but 0 and increasing the connections doesn't seem to effect the tests. Check dmesg and syslogs on the hosts to ensure iptables isn't complaining and TIME_WAIT buckets aren't overflowing anywhere, clients or servers. Nothing in dmesg or syslogs on either side. If all software is new and blah blah blah, would you mind running a test using a pure client (ruby or whatever, just no libmemcached) over localhost to see if you can reproduce the issue there. Sure thing. I'll do that and get an answer to the new vs persistent connection question first thing tomorrow. Quick update to close this thread down: we think we've tracked this to the memcached processes becoming just barely swapped out in some weird circumstances. Sorry. I'm not sure how I missed it originally. Thanks for the feedback and help troubleshooting. Ryan -- To unsubscribe, reply using remove me as the subject.
Tools : phpMemCacheAdmin
Hello all from Brittany(France), where we don't speak very well english, but with (I hope) a lovely accent! Certain time ago we started to use memcached at work (We make news website and classified ads) to drop load off our databases and finally we ended up using it in a regular basis in our new developments. Our developpers and sysadmin wanted a tool to develop, debug and see what is going on memcached server easily. So i develloped a tool named phpMemCacheAdmin : http://code.google.com/p/phpmemcacheadmin/ It's basicaly all we need in one small website with the look feel of the memcached.org website, i hope people will find it usefull. Do not hesitate to give your comments, ideas and corrections. Thanks a lot and keep up the good work Cyrille -- To unsubscribe, reply using remove me as the subject.
Re: Tools : phpMemCacheAdmin
It looks nice, we'll have to give it a try over here. Thanks! On Wed, Apr 14, 2010 at 2:25 PM, c.mahi...@of2m.fr eli...@free.fr wrote: Hello all from Brittany(France), where we don't speak very well english, but with (I hope) a lovely accent! Certain time ago we started to use memcached at work (We make news website and classified ads) to drop load off our databases and finally we ended up using it in a regular basis in our new developments. Our developpers and sysadmin wanted a tool to develop, debug and see what is going on memcached server easily. So i develloped a tool named phpMemCacheAdmin : http://code.google.com/p/phpmemcacheadmin/ It's basicaly all we need in one small website with the look feel of the memcached.org website, i hope people will find it usefull. Do not hesitate to give your comments, ideas and corrections. Thanks a lot and keep up the good work Cyrille -- To unsubscribe, reply using remove me as the subject.
release of spymemcached 2.5
Hi all, I've just posted the 2.5 release of spymemcached. See the summary of changes below. - Matt Release of 2.5 Changes since the 2.4 series: The main new feature of the 2.5 release is support for SASL auth to go along with the same feature in the memcached 1.4.3 and later servers. There is also a new feature which can be used in conjunction with the failure cancel mode to close all connections to memcached servers if there are timeouts against a server. This helps to recover from situations where a memcached server in the list may hard fail. Also notable is this commit: cba26c1 If the String value of the socket address starts with a /, remove it. This does affect Ketama hashing, as it was found there could be some occasional mismatch with libketama. A much larger test was added and to a pretty large degree, compatibility with libketama's hashing is assured. Proceed with caution if you'll be running a mixed environment of 2.5 and pre-2.5 spymemcached clients. To get the old behavior by default, a custom interface is easily implemented. Additionally, there have been a number of bug fixes, comment cleanups some new tests, and some consistency fixes. Changes since 2.4.2: Ahn Seong Hwa (2): New TCP connection timeout feature; if server fails completely, d/c. fix for useless check statement that is for continuous timeout exception counter Blair Zajac (3): Be more generous in the strings that AddrUtil#getAddresses() will parse. Fix AddrUtilTest#testIPv6Host() hostname assertion. Fix consistency issue in ConnectionFactoryBuilder.isDaemon() Dustin Sallings (19): Beginnings of SASL support. A slightly better model for SASL auth. Authentication should allow specification of a mechanism. Refactored broadcast to allow for node selection. Working multi-step auth. Refactored SASL auth for greater reuse. Added support for listing SASL mechanisms. Reformatted callback handler. Don't throw away an exception. Use the socket address as the realm. Better auth API, handles connection drops. Log the bug that causes reconnection on first connect. Replaced Long nanos with long millis for op queue block offer timeout. Ensure the factory builder can be used to specify enqueue block size. Get rid of special constructors for op enqueue timeouts. Do blocking inserts from the cache loader test. Auth fix for mechanisms that have an initial response. If the String value of the socket address starts with a /, remove it. A larger libketama extract for compatibility testing. Greg Kim (1): Implementing read-only methods in MemcachedNodeROImpl - issue86 Kristian Eide (1): Allow user-specified wait time for availability of queue space. Matt Ingenthron (14): Invert the ConnectionFactoryBuilderTest to go with new logic. Document unexpected incr/decr behavior. Issue 48. Various Javadoc completeness. Docs for path to FailureModes on DefaultConnectionFactory. Issue 115. Clarify FutureBoolean, issue 63. Clarify what is planned after a disconnect. Enhance MemcachedNode to know whether auth should happen. Changed AuthTest description to match reality. Manual test to ensure correct connection handling with SASL. Enhanced ConnectionFactoryBuilder test for auth. Minor fixes to SASL reconnect test. Handle auth failures more gracefully; maximum failures. Log operation failures as potential auth failures. Actually use the args to SASLConnectReconnect; shutdown nicely. Bugs fixed/closed: http://code.google.com/p/spymemcached/issues/detail?id=48 http://code.google.com/p/spymemcached/issues/detail?id=115 http://code.google.com/p/spymemcached/issues/detail?id=63 http://code.google.com/p/spymemcached/issues/detail?id=112 http://code.google.com/p/spymemcached/issues/detail?id=111 http://code.google.com/p/spymemcached/issues/detail?id=109 http://code.google.com/p/spymemcached/issues/detail?id=78 http://code.google.com/p/spymemcached/issues/detail?id=104 With others which can be listed here: http://code.google.com/p/spymemcached/issues/list -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (Darwin) iEYEABECAAYFAkvDyG4ACgkQQM0/OE2fY9o/BwCfZBcaORvnKuLFBtjsOcZmSiI9 IFEAnArde+Jn1xkICom2MmQg6h3rFZdz =1oIc -END PGP SIGNATURE- -- To unsubscribe, reply using remove me as the subject.
