> Or instead of "shutdown" it's more of a "interrupt the
> merge if it's in progress" which then doesn't prevent further IO?
At a high level, this would seem like the most valuable approach. But I
think we would want to distinguish between writing new documents and
merges of existing segments. The
[
https://issues.apache.org/jira/browse/LUCENE-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-430:
-
Attachment: lucene-430.patch
I'm attaching a patch that is slightly different from the patch Paul
"Doron Cohen" <[EMAIL PROTECTED]> wrote:
>
> "Michael McCandless" wrote:
>
> > That's correct.
> >
> > On seeing the "shutdown in progress" exception, the current "finally"
> > clause in mergeSegments would revert the internal state of the
> > IndexWriter to be consistent, ie, put back the segment
"Michael McCandless" wrote:
> That's correct.
>
> On seeing the "shutdown in progress" exception, the current "finally"
> clause in mergeSegments would revert the internal state of the
> IndexWriter to be consistent, ie, put back the segments that were in
> the process of being merged into its seg
"Doron Cohen" <[EMAIL PROTECTED]> wrote:
> Michael McCandless wrote on 23/May/2007:
>
> > Actually if autoCommit=true then the only choice is to keep
> > the partial work. In this mode, optimize indeed goes in
> > "stages" (merging mergeFactor segments at a time) and after
> > each stage it commi
Michael McCandless wrote on 23/May/2007:
> Actually if autoCommit=true then the only choice is to keep
> the partial work. In this mode, optimize indeed goes in
> "stages" (merging mergeFactor segments at a time) and after
> each stage it commits a new segments_N file and removes the
> now-merged
Michael Busch wrote on 17/May/2007:
> public static class ExtendedFSDirectory extends FSDirectory {
> ...
> public void flushBuffer(byte[] b, int offset, int size)
> throws IOException {
> if (ExtendedFSDirectory.this.interrupted) {
> throw new IndexWriterInterruptException();
> }
>
>
Improve indexing performance by increasing internal buffer sizes
Key: LUCENE-888
URL: https://issues.apache.org/jira/browse/LUCENE-888
Project: Lucene - Java
Issue Type: Improv
"Steven Parkes" <[EMAIL PROTECTED]> wrote:
> As to what happens in the middle of a merge or optimize: I think it
> might depend on the autoCommit flag. Since an optimize may be done
> in stages, whether the intermediary stages are kept or not is going
> to depend on when the segments file gets upd
