If you are able to leave the IndexSearcher open, and resubmit the
query, and most likely it works the 2nd time around, it really seems
like something intermittent is going wrong with your IO system.
That exception from CheckIndex is just happening when Lucene is trying
to read bytes from
Yesterday, when typing a reply I noticed an error ... the CheckIndex.check
was not checking a good directory.. so the segments not found error was not
correct. I apologize. I made the correction and this is the correct error
that occurs when an i/o error is thrown. I ran the CheckIndex.check me
Can you post some code of the merging process that adds documents to
the current day's index?
It is definitely spooky that CheckIndex reports it cannot find any
segments file. The message in that exception should end with "...:
files: XXX", ie, it says it could not find any segments_N fi
I have seen the error all along... I've tried several different designs...
This problem has always occurred on the current day where the index is
constantly being merged. I am opening one searcher for up to 59 days and
leaving them open but for the current day only, each user get's their own
new
So it sounds like the Input/Output error was in fact because you were
closing the IndexSearcher while an in-flight query was still using it?
Or... are you still seeing that error now that you've switched to
opening a new IndexSearcher for the current day for every query?
It's very costly,
Yes, I am leaving the searchers open for all indexes except for the current
day. The index for the current day is constantly being updated and if I
happen to have the Input/Output error/no segment files found error while
searching the current day then that searcher will continue to return the i/o
Did you resolve the issue where you were closing the IndexSearcher
while searches were still running?
That's where we got to on the last thread:
http://www.nabble.com/Lucene-Input-Output-error-to20156805.html
Mike
JulieSoko wrote:
I am narrowing down this problem that I have had for
