I should mention that my solution does not include replication for the services registry, which is my next step. So I will be interested in what works for you.
On Wed, Oct 15, 2014 at 2:43 PM, Adam Causey <[email protected]> wrote: > I am looking into the HazelcastRegistry. It seems fine so far in a test > environment, but I have not load tested it. A few others indicated they > are using it in a production environment. It's very easy to setup. > > > https://github.com/Unicon/cas-addons/wiki/Configuring-HazelcastTicketRegistry > > We are also moving away from a database replication that is not very > reliable for us. > > > On Tue, Oct 14, 2014 at 4:43 PM, Scott Massari <[email protected]> > wrote: > >> Also running ehcache with JSON service registry. 3 node cluster in both >> test and prod behind Cisco ACE load balancers. >> >> >> ------------------------------ >> Date: Mon, 13 Oct 2014 16:17:28 -0700 >> Subject: Re: [cas-user] HA architectures for CAS >> From: [email protected] >> To: [email protected] >> >> >> We switched from memcache-repcache for tickets and /MySQL for service >> registry to using replicated ehcache for the ticket registry and JSON >> service registry (We manage with puppet, but git/cron would work just as >> well.) This sits behind an apache load balancer. From a clustering >> standpoint it works great for us. >> >> On Mon, Oct 13, 2014 at 12:28 PM, Andrew Morgan <[email protected]> wrote: >> >> On Mon, 13 Oct 2014, Benito J. Gonzalez wrote: >> >> Dear Community, >> >> We are looking to build a High Availability CAS solution for our campus >> rather quickly. We currently have two CAS app VMs sharing tickets with a >> single database as a single point of failure. We have F5 in front to >> load-balance traffic. >> >> What are some high level architectures for HA you have implemented? >> >> >> We have a 2-node CAS cluster behind a load balancer. The ticket registry >> is stored in memcache+repcache. CAS connects to memcache on the localhost >> and it is replicated to the other node. >> >> The service registry is stored in MySQL. CAS continues to process >> authentications while MySQL is down (note: see issue CAS-1458), although >> you cannot make changes to services, of course. >> >> Andy >> >> >> -- >> 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 >> >> >> >> >> -- >> >> --------------------------------------------- >> Casey Feskens <[email protected]> >> Associate Director of Systems Services >> Willamette Integrated Technology Services >> Willamette University, Salem, OR >> Phone: (503) 370-6950 >> --------------------------------------------- >> >> -- >> 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 >> >> > -- 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
