[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500794
]
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: https://issues.apache.org/jira/browse/LUCENE-887
> Project: Lucene - Java
> Issue Type: New Feature
> Components: Index
> Reporter: Michael Busch
> Priority: Minor
> Attachments: ExtendedIndexWriter.java
>
>
> 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:
> http://www.gossamer-threads.com/lists/lucene/java-dev/49008
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
