You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2008/03/09 09:19:46 UTC
[jira] Resolved: (LUCENE-1210) IndexWriter &
ConcurrentMergeScheduler deadlock case if starting a merge hits an
exception
[ https://issues.apache.org/jira/browse/LUCENE-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-1210.
----------------------------------------
Resolution: Fixed
> 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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org