[
https://issues.apache.org/jira/browse/LUCENE-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576927#action_12576927
]
Michael McCandless commented on LUCENE-1210:
--------------------------------------------
Yes, I agree. At some point soon we should do a 2.3.2 point release, and I'll
port this issue back for that.
> IndexWriter & ConcurrentMergeScheduler deadlock case if starting a merge hits
> an exception
> ------------------------------------------------------------------------------------------
>
> Key: LUCENE-1210
> URL: https://issues.apache.org/jira/browse/LUCENE-1210
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.3, 2.3.1
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.4
>
>
> If you're using CMS (the default) and mergeInit hits an exception (eg
> OOME), we are not properly clearing IndexWriter's internal tracking of
> running merges. This causes IW.close() to hang while it incorrectly
> waits for these non-started merges to finish.
--
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]
