Hi, We are very excited to use a production cluster to host our memcached servers for a web service. However I am a little bit unclear as to the behavior in a real-life prod. environment where servers are frequently being rebooted or swapped out and replaced (or new ones added).
I know that you provide a identical list of servers to your clients so that any keys are always mapped to the same server no matter which client is performing the query. But I still have afew questions regarding typical scenarios in our Prod environment: 1) what happens when a server to which a particular key hashes is brought down, and restarted. Would the client (I am using the Java client btw) be able to figure out that a particular server is back up again transparently ? 2) In case one of the servers is brought down for a extended period, would the keys that would have normally hashed continue to incur a DB hit since the hashing function would always map to that machine for a particular key or is there a way to have them start mapping to one of the remaining server instances ? 3) Is there a way to make a live update to the list of servers that a client can use without restarting the client ? Thanks sdeo.
