From 0dfa83934a83f607168b48c48d2b890e55fbddf7 Mon Sep 17 00:00:00 2001 From: Mikael Johansson Date: Sun, 5 Feb 2006 12:00:06 +0000 Subject: [PATCH] Added description of failover behaviour and more information on the effect of the "retry_interval" parameter git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@206459 c90b9560-bf6c-de11-be94-00142212c4b1 --- .../memcache/functions/memcache-addserver.xml | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/reference/memcache/functions/memcache-addserver.xml b/reference/memcache/functions/memcache-addserver.xml index 4fd0e5e5bf..5bf229a8fc 100644 --- a/reference/memcache/functions/memcache-addserver.xml +++ b/reference/memcache/functions/memcache-addserver.xml @@ -1,5 +1,5 @@ - + Memcache::addServer @@ -27,6 +27,14 @@ Memcache::close. You can also use the memcache_add_server function. + + + Failover may occur at any stage in any of the methods, as long as other + servers are available the request the user won't notice. Any kind of + socket or Memcached server level errors (except out-of-memory) may trigger + the failover. Normal client errors such as adding an existing key will not + trigger a failover. + @@ -94,6 +102,14 @@ parameter has any effect when this extension is loaded dynamically via dl. + + Each failed connection struct has its own timeout and before it has expired + the struct will be skipped when selecting backends to serve a request. Once + expired the connection will be successfully reconnected or marked as failed + for another retry_interval seconds. The typical + effect is that each webserver child will retry the connection about every + retry_interval seconds when serving a page. +