lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Busch (JIRA)" <>
Subject [jira] Commented: (LUCENE-887) Interruptible segment merges
Date Fri, 01 Jun 2007 18:21:15 GMT


Michael Busch commented on LUCENE-887:

> I think you are right: just removing the call to flushAfterInterrupt()
> in the catch clause of addDocument() should correct this.  That way
> there is only one place&time (inside shutdown()) where the
> flushAfterInterrupt() is called and this should properly prevent any
> merging from taking place.  Phew!

Cool. I will update the patch.

> Best to make a super stressful thread test case and run in on an N>1
> CPU/core machine to be really sure the different concurrency paths are
> well explored  :) 

Agree. I will work on a test case as well. I can use a 4 core Xeon
machine to run the tests on.

> Interruptible segment merges
> ----------------------------
>                 Key: LUCENE-887
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Index
>            Reporter: Michael Busch
>            Priority: Minor
>         Attachments:
> Adds the ability to IndexWriter to interrupt an ongoing merge. This might be necessary
when Lucene is e. g. running as a service and has to stop indexing within a certain period
of time due to a shutdown request.
> A solution would be to add a new method shutdown() to IndexWriter which satisfies the
following two requirements:
> - if a merge is happening, abort it
> - flush the buffered docs but do not trigger a merge 
> See also discussions about this feature on java-dev:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message