On Mon, Oct 19, 2009 at 03:34, dormando dorma...@rydia.net wrote:
http://blogs.sun.com/trond/date/20090625
^ client side replication.
I like this and feel it's more powerful, since tt scales past two severs
implicitly, and you can enable/disable it per key or key type. So instead
of
Thanks to All,
In a web farm where two memcached server is hosted separately, when
one server is down could all request served from server 2
automatically or we need to remove the dead node explicitly from the
client?
I have tested a scenario:
Key1, Data1 Cached on Server1
Key2, Data2 Cached
I have different domains in a server. I am getting same memcache for
all domains under the server.
Please tell me If any option to get memcaches value based on domains?
On Oct 19, 9:36 am, femy catherine joseph femy@gmail.com wrote:
I have different domains in a server. I am getting same memcache for
all domains under the server.
Please tell me If any option to get memcaches value based on domains?
The easiest way is to include the domain within
Thank you..
Instead of this = $memcache-pconnect('localhost', 11211)
I can use following right ?
$memcache-pconnect('test.com', 11211)
$memcache-pconnect('abc.com', 11211)
On Mon, Oct 19, 2009 at 6:00 AM, Henrik Schröder skro...@gmail.com wrote:
How it works depends on which client you use. If you use the BeITMemcached
client, when one instance goes down it will internally mark it as dead,
start writing about it in the error log, and all requests that would end
On Mon, Oct 19, 2009 at 03:34, dormando dorma...@rydia.net wrote:
http://blogs.sun.com/trond/date/20090625
^ client side replication.
I like this and feel it's more powerful, since tt scales past two severs
implicitly, and you can enable/disable it per key or key type. So instead
of
well this is a bit like mixing together couple of things, i thing if you are
having multiple memcached instance you have to handle it from your app or
write a proxy what checks the memcached servers and distributes the load and
removing the dead one from the pool like load balancers do with http