Chuck Williams wrote:
Hi All,
I found this issue. There is no problem in Lucene, and I'd like to
leave this thread with that assertion to avoid confusing future archive
searcher/readers.
The index was actually not corrupt at all. I use ParallelReader and
ParallelWriter. A kill -9 can leave the subindexes out of sync. My
recovery code repairs this on restart by noticing the indexes are
out-of-sync, deleting the document(s) that were added to some
subindex(es) but not the other(s), then optimizing to resync the doc-ids.
The issue is that my bulk updater does not at present support compound
file format and the recovery code forgot to turn that off prior to the
optimize! Thus a .cfs file was created, which confused the bulk updater
-- it did not see a segment that was inside the cfs.
Sorry for the false alarm and thanks to all who helped with the original
question/concern,
Phew -- glad to hear this! Thanks for bringing closure to this issue.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
