Evening, Question on experiences with replication reliability.
I'm doing a bit of 'burn-in' testing of a new pair of CAS servers (3.5.2, Ehcache, RMI replication). The testing loops in a single thread on randomized loginids from a pool of 20k accounts, submitting a login POST to a random node of the pair, waits a little bit (50ms), then submits the resulting service ticket to its companion node. This generates about 7.5 authentication + service ticket validation transactions per server per second. So I get an ST validation failure on the companion node in about 0.3% (3 in 1000) of the cases. The service ticket cache is set to (the default) synchronous replication + multicast on the RHEL 6 (VMware) VMs, Oracle Java 7, no JVM tuning, Tomcat 6. The servers themselves are spec'd fairly small (1 GB, 1 CPU) when compared to our existing physical CAS production servers. Before I try to dive into what might be a proverbial haystack, is the occasional 'loss' (or delay) of a service ticket considered acceptable? If so, at what rate? For a worst-case scenario (i.e. a fast CAS client), is 50ms realistic? Thanks! Tom. -- 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
