[
https://issues.apache.org/jira/browse/LUCENE-887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544724
]
Michael Busch commented on LUCENE-887:
--------------------------------------
close(false) does not "kill" a merge thread right? So actually
there is no guarantee that close(false) will return within x minutes?
E. g. if a cascading merge is running, then close(false) will wait
for the current merge job to finish, and then abort, meaning not
perform other planned merge jobs of the cascading merge?
But if the current merge job is very big, with huge segments
involved, then it can still take a long time for close(false) to
return?
> 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
> Assignee: 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]
