Hello everyone. I have a system where an indexing-process is running
several times a day, adding documents, and performing an optimize() at the
end of every run.
In addition, we have a web-application (running in tomcat) that is used to
perform searches on the index(es).
The problem (probab
Reopen the Searchers/Readers that are holding the files open.
Aleksander M. Stensby wrote:
Hello everyone. I have a system where an indexing-process is running
several times a day, adding documents, and performing an optimize() at
the end of every run.
In addition, we have a web-application (ru
Hmm, yeah, well thats what I do now...
Shouldn't it be sufficient to do:
searcher.close();
(...)
searcher = new IndexSearcher(indexPath);
Or?
And maybe wrap that in
if(searcher.getIndexReader.hasDeletions())
and possibly (!searcher.getIndexReader.isCurrent())
thanks,
Aleksander
On Wed, 29 A
I'd guess that you're not closing *all* of your searchers.
Which is reinforced somewhat by the fact that bouncing your
Tomcat instance cleans things up. Do you perhaps open
a reader in the initialization code that never gets closed?
Erick
On 8/29/07, Aleksander M. Stensby <[EMAIL PROTECTED]> wrot
