Re: Is memcache add() atomic on a multithreaded memcached?

2010-10-14 Thread elSchrom
Thx for your replies so far. Failover is deactivated in our configuration. This can not be the reason. I think I have to write a little bit more about the circumstances: our 50+ consistent hashing cluster is very reliable on normal operations, incr/decr, get, set, multiget, etc. is not a problem.

Re: Is memcache add() atomic on a multithreaded memcached?

2010-10-14 Thread dormando
our 50+ consistent hashing cluster is very reliable on normal operations, incr/decr, get, set, multiget, etc. is not a problem. If we have a problem with keys on wrong servers in the continuum, we should have more problems, which we currently have not. The cluster is always under relatively

Re: Is memcache add() atomic on a multithreaded memcached?

2010-10-14 Thread elSchrom
On 14 Okt., 10:00, dormando dorma...@rydia.net wrote: our 50+ consistent hashing cluster is very reliable on normal operations, incr/decr, get, set, multiget, etc. is not a problem. If we have a problem with keys on wrong servers in the continuum, we should have more problems, which we

Re: Is memcache add() atomic on a multithreaded memcached?

2010-10-14 Thread dormando
Yeah, right. :-) Restarting all memd instances is not an option. Can you explain, why it is not possible? Because we've programmed the commands with the full intent to be atomic. If it's not, there's a bug... there's an issue with incr/decr that's been fixed upstream but we've never had a

Re: Is memcache add() atomic on a multithreaded memcached?

2010-10-14 Thread elSchrom
Hi Diez, On 14 Okt., 11:39, Dieter Schmidt flatl...@stresstiming.de wrote: For me it sounds like a configuration problem on the webservers or an availability/accessability issue. If for example all machines are accessable the locking key resides on maschine x. If one of the servers

Re: Is memcache add() atomic on a multithreaded memcached?

2010-10-14 Thread elSchrom
On 14 Okt., 14:01, Dieter Schmidt flatl...@stresstiming.de wrote: What happens if the add cmd failes because of an unlikely network error? The situation is: two different clients are doing an add() with the same key at the same time. Both are getting true (assuming that this key has to be on

1MB limit on object size

2010-10-14 Thread Sakuntala
Hi, I am using memcached server version 1.4.4 on Linux and spy memcached client version 2.4.2 I performed a test by storing and retrieving objects of size 1.8MB and 3.6MB. I am able to retrieve the objects successfully without any error. My load tests show some timeout exceptions when memcached

Silicon Valley and Memcache

2010-10-14 Thread Dave Haverstick
We are recruiting for two Data Warehousing/Cloud Computing software companies in the South Bay of Silicon Valley. One is a block from the Cal-train. They are looking for Sr Software Engineers with a C++ and Memcached background and Sr QA Engineers. Please call me or suggest and we can discuss

Re: Is memcache add() atomic on a multithreaded memcached?

2010-10-14 Thread dormando
On 14 Okt., 10:31, dormando dorma...@rydia.net wrote: Yeah, right. :-) Restarting all memd instances is not an option. Can you explain, why it is not possible? Because we've programmed the commands with the full intent to be atomic. If it's not, there's a bug... there's an issue with