Thanks a lot. I am running my application on windows.
As you suggested I am now closing the indexreader after every read and it
has now solved the problem. My only question is how costly it would be to
close and open the indexreader every time. Is it too heavy in terms of
performance?
-Anand.
On
Opening a single IndexWriter and using it 'forever' is the right way
to do NRT indexing+searching, and merging should keep segment counts
in check.
Are you on Windows? Is it possible you're not closing every
IndexReader you opened? This will cause files to be held open and
then IndexWriter can't
Let me explain the usage scenario:
I have an application with frequent doucment updates and it uses NRT
reader. I also have a background thread which calls commit on the
IndexWriter on a regular interval. There is one instance of IndexWriter
which is created and it is never closed.
The problem is
Opening a single IndexWriter and using it 'forever' is the right way
to do NRT indexing+searching, and merging should keep segment counts
in check.
Are you on Windows? Is it possible you're not closing every
IndexReader you opened? This will cause files to be held open and
then IndexWriter can't
Let me explain the usage scenario:
I have an application with frequent doucment updates and it uses NRT
reader. I also have a background thread which calls commit on the
IndexWriter on a regular interval. There is one instance of IndexWriter
which is created and it is never closed.
The problem is
Hi,
Currently Luke is not the part of Lucene, you should check Luke project in
Github.
https://github.com/DmitryKey/luke
Here is the Issue for lucene 5.
https://github.com/DmitryKey/luke/issues/21
I'm now trying to make Luke support Lucene 5.x in my local branch.
Pull requests from other develop
