On 8/7/2013 12:18 PM, Aaron Bennett wrote:
What we're planning for scheduled maintenance, is using memcached-tool
to push a given server's cache to another server before shutting it down
for maintenance... something as simple as this..
./memcached-tool localhost dump | nc <otherhost> 11211
My (limited and possibly inaccurate) understanding of memcached,
specifically the client implementation for CAS, is that a particular key
is hashed, and based on the outcome of that, the client looks for it on
a specific node. So I'm not sure what good a copy of the data on another
node will do if the client doesn't know to look for it there?
Do you specifically pick the other node to transfer it to based on
calculating what the backup node hash would be for the failed node? And
in a failure mode, does the client actually try to do an initial read
from the backup node, or just write out new data to it?
--
Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/
Operating Systems and Network Analyst | [email protected]
California State Polytechnic University | Pomona CA 91768
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
