lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele Bini (JIRA)" <j...@apache.org>
Subject [jira] Commented: (LUCENE-1210) IndexWriter & ConcurrentMergeScheduler deadlock case if starting a merge hits an exception
Date Mon, 10 Mar 2008 10:09:46 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576924#action_12576924
] 

Michele Bini commented on LUCENE-1210:
--------------------------------------

Uhm, shouldn't the patch be committed in the 2.3 branch, too, as it affects 2.3.1?

> 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


Mime
View raw message