Hi Guys,
So I think I’ve figured it out… We use a common merge scheduler to handle
merges across all of our indices. When the SearchManager starts up, it triggers
a merge operation, this merge request pushes a task on the merge scheduling
queue and we only allow one merge request per index writ
No exception at all… and that’s the crazy part. I create a new IndexWriter and
then immediately create a new SearcherManager using that freshly-created
IndexWriter. Granted, I don’t actually do anything with the IndexWriter before
passing it to the SearcherManager, but no exceptions are thrown e
Presumably no exception is thrown from the new IndexWriter() call?
I'd double check that, and try some harmless method call on the
writer and make sure that works. And run CheckIndex against the
index.
--
Ian.
On Tue, Jan 6, 2015 at 5:05 PM, Brian Call
wrote:
> Hi Tomoko,
>
> Thank you f
Hi Tomoko,
Thank you for your response! We’ve actually never seen this before in the
three+ years of developing using Lucene 3.6.x. The only time we’ve ever seen
this kind of exception is once recently in a running production system and it
caught me way off guard. We’re deploying on Suse linux
Hi,
How often does this error occur?
You do not tell the lucene version, but I guess you use lucene 3.x
according to the stack trace...
IndexWriter would not be closed until IndexWriter.close() method is called
explicitly.
https://github.com/apache/lucene-solr/blob/lucene_solr_3_6_2/lucene/core/sr
