[cas-dev] high availability issue of CAS

[Lin George]

Thanks Scott!

1.

From your reply below, your recommended way is to set replication information between clustered CAS servers so that all servers contain all user session information, i.e. all cache of all clustered CAS servers contain idential information? Then when one server is down, the other server could be used as backup?

(For example, if a new user login from one CAS server, the CAS server stores user credential/session information in its cache, and then replicate the information into another CAS server cache?)

2.

I am not sure how many user data is able to be stored into one server, do you have any information? The target user size is about 200k users (including users which are graduated) for my school. Thanks.

regards,
George

--------------------
Most of our high-availability clustering shares information across
servers such that if one goes down the other can handle whatever the
downed server was doing.

-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia