There is no server-side concept of master-slave. memcached never talks to any other servers; it only responds to requests from clients. Any clustering or failover you do will need to be driven from the client. What you could do is set up a client to write to two different memcached boxes and read from one randomly; if that request fails, then read from the other. This way, if one goes down, you still have all the data in cache.
Here's an article I found (but didn't read yet): http://www.linuxjournal.com/article/7451 ~Ryan On Mon, Mar 3, 2014 at 9:36 PM, Ranjit D'Souza <bernard....@gmail.com>wrote: > Thank you > > Is there any concept of master-slave configuration (like in Redis), and > promoting the slave to master? > > Can you point me to a document or wiki link that gives more information on > how to set up a memcached cluster? > > -- > > --- > 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 memcached+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- --- 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 memcached+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
