If you're not familiar with how Memcache and repcache work, I recommend reading up on their documentation:
http://www.danga.com/memcached/ http://repcached.lab.klab.org/ You'll want to understand how they work and their implications if you're considering deploying them. Cheers, Scott On Wed, Jul 1, 2009 at 5:56 PM, venu.alla <[email protected]> wrote: > hi, > I see that the memcacheTicketRegistry bean takes a list of the memcache > servers in the form host:ip. We will be doing some quick tests, but thought > I will ask the forum following questions anyways. > > > 1. Does the memcache client do redundant writes to all the hosts in the > list or does it only do failover writes? > > 2. are reads redundant or failover only. By that I mean, if a request goes > to node-A and if the serviceTicket presented is not found there, will it > look up in node-B? > > 3. If it is redundant write and read, then why do we need repcache? Is it > because, if one of the node-1 restarts, repcache will sync the restarted > node to the current state of node-2? > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
