Hi everyone, A few questions for those of you who are using a distributed or high availability CAS implementation (i.e., more than one server in a pool of some sort):
1. Which technology are you using for your ticket repository? 2. How many CAS servers are you running? 3. How many ticket repository servers? 4. Are CAS and the ticket repository running on the same server or different? 5. What's your average / peak load in terms of number of logins per second/minute/something? 6. What problems have you had, if any? To answer these for us: 1. Mongo DB 2. 5 3. 5 4. Same servers 5. 30,000 STs validated in an average day. 6. Under peak load (like during course registration, when all the students try to log in right at 8:00am), we have had problems with CAS working fine for TGT and ST creation, but then ST validation fails because the ticket isn't in the database yet. We're pretty sure that the problem has to do with how Mongo DB writes things to disk, and think it might be possible to fix it with some tweaking, but advanced Mongo DB configuration seems to be somewhat of a black art, and the documentation frankly sucks. The decision to use Mongo DB for the ticket registry was made for no better reason than "...well, we're already using it for the service registry, and we don't know much about any of the other options anyway, so..." :-). So maybe it wasn't the best choice--certainly there's no reason that tickets actually need to reside on disk. And now we're thinking it might be easier to just replace it with a better technology for the ticket registry rather than trying to figure out the magical incantations that might make it work better. Hence the questions above -- we'd like to know what other folks' experiences have been, so that maybe we can make a better choice the second time around. Thanks, --Dave -- DAVID A. CURRY, CISSP *DIRECTOR OF INFORMATION SECURITY* THE NEW SCHOOL • INFORMATION TECHNOLOGY 71 FIFTH AVE., 9TH FL., NEW YORK, NY 10003 +1 212 229-5300 x4728 • david.cu...@newschool.edu -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/a91a5905-6809-46cb-9e56-e2e03e879516%40apereo.org.
