[
https://issues.apache.org/jira/browse/LUCENE-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049786#comment-13049786
]
Michael McCandless commented on LUCENE-3197:
--------------------------------------------
Right, this has been the intended semantics of a background optimize for some
time, ie, when it returns it only ensures that whatever was not optimized as of
when it was called has been merged away.
This already works correctly for newly added docs, meaning if you continue
adding docs / flushing new segments while the optimize runs, it knows that the
newly flushed segments do not have to be merged away.
But for new deletions we are not handling it correctly, which leads to the
forever running merges.
> Optimize runs forever if you keep deleting docs at the same time
> ----------------------------------------------------------------
>
> Key: LUCENE-3197
> URL: https://issues.apache.org/jira/browse/LUCENE-3197
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 3.3, 4.0
>
>
> Because we "cascade" merges for an optimize... if you also delete documents
> while the merges are running, then the merge policy will see the resulting
> single segment as still not optimized (since it has pending deletes) and do a
> single-segment merge, and will repeat indefinitely (as long as your app keeps
> deleting docs).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
