I've been trying to track down a problem we have been seeing, and it looks like under heavy load that memcached can return keys with a NULL value, or keys from a different request. This is all using PERL (ick).
I first query the server to get all of the currently known keys. I then split the keys into 2 different arrays (with 500 -> 800 entries each with no overlap), and call BEMemd::get_multi alternately with each array. I then compare what is returned to what I expect. This is all done with in up to 5 separate processes talking to the server at once (I also have 5 write tests adding/reading/deleting new data, and a calculate script that places more load on the server). All of these processes are the same (non-root) user. I have the system configured with a single memcached server. While most of the time, everything is all happiness and rainbows, sometimes I get back a key with a NULL value, and sometimes I get back a key/value from the other array (so I request array_1, and get many keys from array_1, but also a key from array_2). Has anyone else seen this problem? FWIW, I also see this with 1.4.5, I haven't tried any version between those, nor anything after 1.4.22. Thanks, -- --- You received this message because you are subscribed to the Google Groups "memcached" group. To unsubscribe from this group and stop receiving emails from it, send an email to memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
