It's not on the second server. I suggest you read this:
http://code.google.com/p/memcached/wiki/NewOverview
/Henrik
On Wed, Oct 5, 2011 at 18:38, saad smouiz...@gmail.com wrote:
hello,
I try to set two memcache server a key. When I get this key from the
first server it work but when I try
Hi,
Note that I am using xmemcached client connection pool.
What I observed is that the there are lot of connections and
disconnection happening to the server which stores less data.
I ran memcached in verbose mode I got the following error :
Failed to read, and not due to blocking:
errno: 104
Okey,
So, if I understand correctly, it doesn't write on both servers at the
same time but it only allows to have a larger storage capacity, right?
On 6 oct, 11:46, Henrik Schröder skro...@gmail.com wrote:
It's not on the second server. I suggest you read this:
Hello all,
Nice to be a part of the memcached community.
Is there any way, using the current libmemcached library, to
dynamically assign expiration to certain keys ?
What I am trying to do is the following :
# expire key in 100 seconds
set key value 100
# after 10 seconds, decide to modify the
We are planning to deploy a memcached cluster of 40 odd machines and
were wondering about mgets and the size of the cluster.
We could either:
- have all the machines in one cluster, which would mean that an mget
on a set of keys could potentially span the entire cluster
- partition our
Right. It does sound like we'll have to conduct some experiments.
Would've been nice to get some other inputs though.
We might make 2000-3000 mgets/sec. 100-500 keys each.
On Oct 6, 1:38 pm, dormando dorma...@rydia.net wrote:
We are planning to deploy a memcached cluster of 40 odd machines
Right. It does sound like we'll have to conduct some experiments.
Would've been nice to get some other inputs though.
We might make 2000-3000 mgets/sec. 100-500 keys each.
It's straight up math.
if (keylength * keycount tcp_buffer) - latency benefit from having
shorter mgets (or just
