Home | Forums | Membase | Memcached Server 1.0.3

memcache is storing keys but no values

4 replies [Last post]
Wed, 04/07/2010 - 09:57
jim
Offline
Joined: 03/26/2010
Groups: None

I have deployed NSMS to my qa environment and was able to setup the server and get them running. I have setup a web client that inserts items to this. I can see in the NS dashboard that the keys are getting to the server but no values are ever being recieved. Is there any reason this might happen?

I have disabled the firewalls on both machines. I cant imagine this is a port issue since the server is getting the key and not the values. When running on my local machine I can see that values are being inserted and deleted so I would assume it has to do with networking or configuration. Any help would be welcome.

Also with respect to the dashboard that is provided, when you turn on the test server option does that submit test data from the NSMS or the dashboard? Thus if you were viewing the dashboard on a different machine the test would be sending data from that other machine.

Thanks,
Jim

Top
Wed, 04/07/2010 - 10:27
sean
Offline
Joined: 03/15/2010
Groups: None

Hi, Jim.

How is it you're determining no values are being stored? Note that the top keys table will show *any* operations on keys, including misses; no set operation ever has to occur for a key to show up in that list.

You can see the actual data stream using WireShark ([url]http://www.wireshark.org/[/url]) on either the client or the server looking at port 11211; WireShark has support for the binary memcached protocol and will show you what commands are being sent, and what the keys and values are.

Top
Thu, 04/08/2010 - 10:48
jim
Offline
Joined: 03/26/2010
Groups: None

Thanks for the wireshark comment. That helped solve the problem. I found that while using the enyim 2.0 beta that when you try to store items with a datetime that the request went to the memcached server with an expiration that is the time in seconds between the date I gave and 1/1/1970, which is longer than the 30 day period that memcache expected. I am not sure why this worked for me when working on my machine and both the website and NSMS were local. I have changed my code to always pass the expiration as a timestamp and this sends the expiration time as the number of seconds I actually want the item to be cached.

Is there a way for me to use wireshark to track packets that never leave my box?

Thanks,

Top
Thu, 04/08/2010 - 10:52
sean
Offline
Joined: 03/15/2010
Groups: None

If they don't show up on the ethernet interface, they should show up on the loopback interface. It'll be called lo or lo0 or loopback, depending on your platform.

Top
Fri, 04/16/2010 - 05:57
laervalp
Offline
Joined: 04/16/2010
Groups: None

I too have run into this issue. Specifying expiration as a duration in seconds works fine, but using a datetime value (i.e. a Unix time value) seems to result in instant expiry. For the record, I'm running the Northscale Memcache Server on a Windows 2008 R2 machine. Do we perhaps have an issue with the unix timestamps on the Windows port/environment?

I can probably switch our code to use durations, but I'm just not clear if anyone is looking at the specific date issue? Also, is there a way to know when you've made new releases?

Thanks very much. This looks like a very promising product!

Top