I've never looked at the JMX views, but mayfly-aged searchers are both expected AND undesirable. Every Solr commit (every persisted change to the index) forces creation of a fresh searcher with fresh caches. And the OAE does a lot more Solr commits than would normally be recommended. So what you're seeing reflects a known performance issue that we continue to work on.
Best, Ray On 6/14/12 10:40 AM, Berg, Alan wrote: > Hi, > > Potentially a newbie question, so be warned. I am looking through JMX at a > stress test that loads in lots of little files to a demo version of Sakai OAE. > > The managed beans give lots of valid information apart for the > solrindexsearcher. Apparently every time a small file is uploaded or a group > is made a new managed bean appears and then dies quickly. This gives a very > fast changing view in Jconsole. Is this normal or a sign that > solrindexsearchers are being created and destroyed too quickly and another > design pattern like a queue is needed? > > See screengrab, the searcher bean id is being replaced very often. > > Alan Berg > > Group Education and Research Services > Central Computer Services > University of Amsterdam > > > > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev > _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
