There is no 'logout'. There is no permanent state in Solr beyond the Lucene index. There are caches, but these do not require any termination. The Lucene API has very solid self-protection for the indexes and Solr uses the API in the right way.
If you run a Solr distribution in a standard servlet container, you can just use the servlet's shutdown protocol. If you call a commit with waitFlush=true, then do not index any records, you can kill the servlet process. On Fri, Aug 21, 2009 at 7:45 AM, Fuad Efendi <f...@efendi.ca> wrote: > I can't understand: do you use several web applications in a same > container? > Are you trying to close shared SolrCore when one of many users (of another > application) logs off? > > Usually one needs to clean up only user-session specific objects (such as > non-persistent shopping cart)... > > > -----Original Message----- > From: Rahul R [mailto:rahul.s...@gmail.com] > Sent: August-21-09 1:20 AM > To: solr-user@lucene.apache.org > Subject: Implementing a logout > > Hello, > Can somebody give me some pointers on the Solr objects I need to clean > up/release while doing a logout on a Solr Application. I find that only the > SolrCore object has a close() method. I typically do a lot of faceting > queries on a large dataset with my application. I am using Solr 1.3.0. > > Regards > Rahul > > > -- Lance Norskog goks...@gmail.com
