are you running memcache plain on each of the three nodes?
Yes, one on each CAS node, no repcache. I am working to dispel the
notion that repcache is required or even beneficial for
MemCacheTicketRegistry. See the discussion here for more info:
http://jasig.github.io/cas/installation/Memcach
is a compelling reason for the group to
upgrade.
Thanks again for the insight,
-Michael.
-Original Message-
From: Marvin S. Addison [mailto:marvin.addi...@gmail.com]
Sent: Wednesday, July 03, 2013 1:58 PM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] ehCache, heap, timeouts?
>
We are currently running a three node cluster with ehcache configured
to replicate to the other two nodes in the cluster. Going
memcache/repcache would put us in a 2 node cluster?
Not necessarily. The determining factor is the total amount of memory
needed to store all ticket-granting and servi
com]
Sent: Saturday, June 29, 2013 6:25 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] ehCache, heap, timeouts?
> What I would like is for the replication to use either async or a
> timeout value where if the other peer nodes are under duress, the
> sending threads don't block; rat
> What I would like is for the replication to use either async or a timeout
> value where if the other peer nodes are under duress, the sending threads
> don't block; rather they timeout quickly, or send the tickets a bit more
> asynchronously, without the client on the hook.
Asynchronous replicat
