Hi,
Solr apparently writes loads of error messages with every update, commit,
search etc. Everything seems to be fine, searching and indexing is correct
and fast, but we are concerned it might affect other parts of the system if
they are in fact symptoms of errors internal to Solr. It seems that o
Hossman, thank you for clearing that up. The reason I create a new searcher
for every search is that the index is frequently updated, and as far as I
could read the documentation, a searcher will not detect changes in the
index that occured after it was opened. I tried using just one searcher, but
e triggered by low
> descriptors). SolrIndexSearcher objects are reference counted and
> closed when no longer in use. This means that SolrQueryRequest
> objects must always be closed or the refcount will be off.
>
> Not sure where you could start except perhaps trying to verify the
t; number of live SolrIndexSearcher objects.
>
> -Yonik
>
> On Dec 20, 2007 8:20 AM, amamare <[EMAIL PROTECTED]> wrote:
>>
>> I have an application consisting of three web applications running on
>> JBoss
>> 1.4.2 on a Linux Redhat server. I'm us
The issue you are seeing looks identical to the
> one I am seeing. I started a thread about this same issue on Monday. Are
> you also running Solr 1.2?
>
> On Dec 20, 2007 8:20 AM, amamare <[EMAIL PROTECTED]> wrote:
>
>>
>> I have an application consisting o
I have an application consisting of three web applications running on JBoss
1.4.2 on a Linux Redhat server. I'm using Solr/Lucene embeddedly to create
and maintain a frequently updated index. Once updated, the index is copied
to another directory used for searching. Old index-files in the search
d
