| 2013-07-23 15:52:45 |
cube45 |
description |
Hi,
I am currently trying to test libmemcached but I am facing a strange behaviour:
Let's say we have two memcached servers (A and B) and a data d.
I want to put this data on the servers so that it will be available.
The key hash seem to designate the node A as the primary and B as the replicate.
If B is down, the data is written only on A.
But if A is not up, d is not automatically written to B and is lost.
Is this what was intended?
I saw some lines on storage.cc that let me suppose that if the first node does not succeed in saving the data, then it is not saved at all.
Regards,
cube45 |
Hi,
I am currently trying to test libmemcached but I am facing a strange behaviour:
Let's say we have two memcached servers (A and B) and a data d.
I want to put this data on the servers so that it will be available.
The key hash seem to designate the node A as the primary and B as the replicate.
If B is down, the data is written only on A.
But if A is not up, d is not automatically written to B and is lost.
Is this what was intended?
I saw some lines on storage.cc that let me suppose that if the first node does not succeed in saving the data, then it is not saved at all.
I'm using libmemcached 1.0.16 with binary protocol, CAS support and number of replicas to 1
Regards,
cube45 |
|
