Memcache, as far as I know, uses a hash of the key to determine which server to write to (and then with repcache, its replicated to its pair, which you configure).
-Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Tue, Oct 14, 2008 at 10:38 AM, Andrew Ralph Feller, afelle1 < [EMAIL PROTECTED]> wrote: > Scott, > > I've looked at the sample configuration file on the JA-SIG wiki, however I > was curious how memcached handles cluster membership for lack of a better > word. One of the things we are getting burned on by JBoss/Jgroups is the > frequency the cluster is being fragmented. > > Thanks, > Andrew > > > > On 10/14/08 8:58 AM, "Scott Battaglia" <[EMAIL PROTECTED]> wrote: > > We've disabled the registry cleaners since memcached has explicit time outs > (which are configurable on the registry). We've configured it by default > with 1 gb of RAM I think, though I doubt we need that much. > > -Scott > > -Scott Battaglia > PGP Public Key Id: 0x383733AA > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > > On Mon, Oct 13, 2008 at 11:41 PM, Patrick Hennessy <[EMAIL PROTECTED]> > wrote: > > > I've been working on updating from 3.2 to 3.3 and wanted to give > memcached a try instead of JBoss. I read Scott's message about > performance and we've had good success here with memcached for other > applications. It also looks like using memcached instead of JBoss will > simplify the configuration changes for the CAS server. > > I do have the JBoss replication working with CAS 3.2 but pounding the > heck out of it with JMeter will cause some not so nice stuff to happen. > I'm using VMWare VI3 and configured an isolated switch for the > clustering and Linux-HA traffic. I do see higher traffic levels coming > to my cluster in the future, but I'm not sure if they'll meet the levels > from my JMeter test. (I'm just throwing this out there because of the > recent Best practice thread.) > > If I use memcached, is the ticketRegistryCleaner not needed anymore? I > left those beans in the ticketRegistry.xml file and saw all kinds of > errors. After taking it out it seems to load fine and appears to work, > but I wasn't sure what the behavior is and I haven't tested it further. > What if memcached fills up all the way? Does anyone have a general > idea of how much memory to allocate to memcached with regards to > concurrent logins and tickets stored? > > Thanks, > > Pat > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Patrick Hennessy ([EMAIL PROTECTED]) > > Senior Systems Specialist > Division of Information and Educational Technology > Delaware Technical and Community College > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > > > ------------------------------ > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > > -- > Andrew R. Feller, Analyst > Information Technology Services > 200 Fred Frey Building > Louisiana State University > Baton Rouge, LA 70803 > (225) 578-3737 (Office) > (225) 578-6400 (Fax) > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > >
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
