Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have 2 memcached servers configured and use the Eniym client. When one of the server is down, it appears this server is added to the deadServers list (ServerPool.cs) and tries to resurrect the server every 10seconds (we have configured deadTimeOut to be 10seconds). Attempting to connect to the failed server causes a TCP timeout, the pages take a long time to load which results in bad user experience.

1) What is the standard way of resolving this issue? There are some posts about removing the server from the deadServers list. Is it okay to do this?

2) What is the recommended deadTimeOut setting (I understand by default it's 2 mins and we've changed it to 10seconds in our implementation)

3) Am I correct in my understanding that the cached data is not replicated across Server 1 and Server 2? If Server 1 is down, then it goes to the database to fetch these values (and it doesn't really check Server2)?

Any help is really appreciated.

share|improve this question
up vote 1 down vote accepted
  1. As a general rule, it's normally expected that you just accept that the cache may or may not have what you want.
  2. It depends on the scenario, but it sounds like you might benefit from a higher one. There's no great loss having it higher (2-5 minutes).
  3. Yes. Memcache will usually cache the values again on Server 2 (after fetching from the DB because Server 1's cache is unavailable).

You probably also lower your TCP timeout being used to reconnect to the possibly-dead server.

share|improve this answer
In larger farms, how is this configured? When one of the memcache server goes down, I think it's unacceptable to wait for a TCP timeout which may easily take around 20-30 seconds and user's experience would be degraded till that server is back up. "You probably also lower your TCP timeout " -> Is this the deadTimeOut setting? – user25164 Nov 9 '09 at 22:31
Any help is appreciated. Thanks – user25164 Nov 10 '09 at 16:37
It depends on the features of the API you're using, but at least some let you specify how long you want to wait for results, before assuming the server has died. eg. in PHP, the "timeout" option to the connect method: Use a lower timeout there to detect the failure quickly. Remember though that it'll only be an issue once every {deadTimeOut} seconds, inbetween it'll remember that the server is offline. You should read the FAQ:…? – mibus Nov 10 '09 at 20:21
Possibly also:…? – mibus Nov 10 '09 at 20:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.