*"release any SOLR resources" - no need.*
My query is answered. Thank you.
Regards
Rahul
On Mon, Aug 24, 2009 at 12:32 AM, Fuad Efendi wrote:
> Truly correct:
>
> - SOLR does not create HttpSession for user access to Admin screens (do we
> have any other screens of UI?)
> - SolrCore is shared
Truly correct:
- SOLR does not create HttpSession for user access to Admin screens (do we
have any other screens of UI?)
- SolrCore is shared object; closing it and reopening for each user session
is extremely expensive; this object requires gigabytes of RAM in even
simplest scenario
User doesn't
Just clarifying : My query was more specific to Solr. I wanted to check if
there are any Solr resources that are session-specific that we need to
release.
*>> 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
Sorry, hit 'send' too soon. You can kill the servlet process, but it is much
better to use the servlet container's shutdown protocol.
On Sat, Aug 22, 2009 at 6:46 PM, Lance Norskog wrote:
> There is no 'logout'. There is no permanent state in Solr beyond the Lucene
> index. There are caches, but
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
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
