I understand that in most cases you don't need this. However to me it 
doesn't look like a seperate project (as it's bound to memcached, and can't 
be used "standalone"). Actually more like an enhancement/feature. In that 
case distros would distribute the binarie packages without this capability 
built-in. But for someone who wants to use it he could just configure it 
through make and compile. Probably somebody at memcached kept this feature 
out for some (probably good) reason.

Op dinsdag 5 augustus 2014 20:06:16 UTC+2 schreef LesMikesell:
>
> On Tue, Aug 5, 2014 at 10:45 AM, PenguinWhispererThe 
> <[email protected] <javascript:>> wrote: 
> > Hi all, 
> > 
> > I wonder what the added value for repcached 
> > is(http://repcached.lab.klab.org/). 
> > It replicates the objects to both configured nodes. So you can read the 
> > cached value on all nodes even if it was added through the memcached on 
> the 
> > other node. 
> > 
> > In the normal memcached there is a constant hash algorithm so you will 
> hit 
> > the correct server when reading a previously set value. 
> > When this server goes down I assume you just "cache-miss" and get your 
> data 
> > directly from the database and then cache it on another memcached node? 
>
> Yes, that is the normal memcache approach, and depending on your hash 
> choice you can either 'just fail' for a portion of the hash range 
> until the node is back or rebalance across the remaining nodes.  As 
> long as you have a reasonable large number of nodes and a reasonably 
> fast database you can tolerate having some nodes down some of the 
> time. 
>
> > I would assume repcache would give some kind of HA however I don't see 
> how 
> > this can't be accomplished by the normal memcached. 
> > Ok, you loose cache but it will be cached on another node again. In that 
> way 
> > it actually seems like repcached adds overhead. 
>
> It isn't necessary in the general case - which is probably why it is a 
> separate project. It might help if you have a small number of nodes or 
> a database that can't handle a flurry of cache misses. 
>
> -- 
>    Les Mikesell 
>      [email protected] <javascript:> 
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to