Sure thing. On Ubuntu setting up a single memcached node is as simple as `sudo apt-get install memcached`. For a high-availability cluster, just follow the instructions here:
http://www.howtoforge.com/how-to-install-repcached-memcached-replication-for-high-availability-over-2-nodes-on-ubuntu-11.04 Then on the CAS side, you’d simply configure a custom ticketRegistry.xml in your overlay, inside `/src/main/webapp/WEB-INF/spring-configuration/ticketRegistry.xml` https://gist.github.com/divideby0/a28c692c861501d78655 Ehcache is also certainly an option and is likely the path-most-travelled since it’s the de facto caching solution for Java. In my experience, it’s a bit harder to configure ehcache for high availability, but that could just be my own lack of expertise. -- Build Smarter Software. Cedric Hurst, Principal Spantree Technology Group, LLC 1144 W Fulton Market, Suite 120, Chicago, IL email: [email protected] | phone: 888.386.5501 web: http://www.spantree.net On October 6, 2014 at 1:52:09 PM, Adam Causey ([email protected]) wrote: Hi Cedric, We are only planning a backup server in AWS at the moment and one or two servers onsite. Would this still be an option? Where could I find documentation on the Memcached replication? On Mon, Oct 6, 2014 at 2:46 PM, Cedric Hurst <[email protected]> wrote: If you’re on EC2, the Memcached replication option is worth considering. That way you can use AWS’s Elasticache offering to spin up your Memcached cluster, replication, etc. -- Build Smarter Software. Cedric Hurst, Principal Spantree Technology Group, LLC 1144 W Fulton Market, Suite 120, Chicago, IL email: [email protected] | phone: 888.386.5501 web: http://www.spantree.net On October 6, 2014 at 1:34:34 PM, Adam Causey ([email protected]) wrote: Hello, Currently we have a customized setup of HA clustering of CAS 3.5.2 which involves two servers (one primary, one failover) with a mySQL master-master replication. The database caches ticket-granting tickets in case of failover to the 2nd server. We've had multiple issues with the master-master replication, and we are also planning to introduce a 3rd server in the cloud. Is the EhcacheTicketRegistery still the best method for clustering multiple servers? We will have to use RMI since multicasting is not an option in AWS. If we use the EhcacheTicketRegistery, can we switch to a load balanced setup instead of having a primary/failover setup? Thank you, Adam Causey Virginia Commonwealth University -- 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
