...or better still, when one of your cache servers go down, you hit the databse (or other cache servers) till the broken one is fixed !!!
On 4 March 2011 01:42, dormando <dorma...@rydia.net> wrote: > > Hi all, > > I know I'll get blasted for not googling enough, but I have a quick > question. > > > > I was under the impression memcached servers replicated data, such that > if i have 2 servers and one machine goes down the data would all still be > > available on the other machine. this with the understanding that some > data may not yet have been replicated as replication isn't instantaneous. > > > > Can you clarify for me? > > > > thx, > > > > -nathan > > I sound like a broken record about this, but I like restating things > nobody cares about; > > - memcached doesn't do replication by default > - because not replicating your cache gives you 2x cache space > - and when you have 10 memcached servers and one fails... > - ... you get some 10% miss rate. > - and may cache 2x more crap in the meantime. > > if your workload really requires cache data never disappear, you're > looking more for a database (mysql, NoSQL, or otherwise). > > the original point (and something I still see as a feature) is the ability > to elastically add/remove cache space in front of things which don't scale > as well or take too much time to process. > > For everything else there's > mastercard^Wredis^Wmembase^Wcassandra^Wsomeotherproduct > > -Dormando
