Unfortunately my target index is fully optimized so only one segment.
So CheckIndex won't be useful.
I'll reindex from scratch and also check for hardware issues.
Hopefully it won't get corrupted again.
Thanks for your help.
-
Cristian Vat
On Wed, Oct 20, 2010 at 22:58, Michael McCandless
wrot
Not recoverable automatically.
But you can run CheckIndex -fix -- it removes the segment(s) that has
the corruption (losing all docs in that segment).
Searches appear fine because we don't do this check ("docs out of
order") during searching, but results are likely wrong when they hit
that segmen
Corruption in the sense that it isn't recoverable or is there
something I might be able to do?
The index opens up without problems in Luke and there's an application
using it for searching without problems (apparently)
It's actually an application with a (possibly) hourly update, so
finding the l
This looks like index corruption.
But: are you able to reproduce this corruption, eg on different
machines? I'd love to see how :)
Your usage (using addIndexesNoOptimize to add indices) looks fine.
Mike
On Wed, Oct 20, 2010 at 2:45 PM, Cristian Vat wrote:
> Hello,
>
> I've been running into a
