lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ning Li" <ning.li...@gmail.com>
Subject Re: [jira] Commented: (LUCENE-555) Index Corruption
Date Fri, 27 Oct 2006 15:12:13 GMT
> It's only upon successfully writing the new segments that Lucene will write a new "segments"
file referring to the new segments.  After that, it removes the old segments.  Since it makes
these changes in the correct order, it should be the case that disk full exception never affects
the already written index.

Lucene could produce an inconsistent index if addIndexes(Directory[])
does not run to its completion. The following is my recent comment on
another issue.

"This makes me notice a bug in current addIndexes(Directory[]). In
current addIndexes(Directory[]), segment infos in S are added to T's
"segmentInfos" upfront. Then segments in S are merged to T several at
a time. Every merge is committed with T's "segmentInfos". So if a
reader is opened on T while addIndexes(Directory[]) is going on, it
could see an inconsistent index."

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message