You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Christoph Goller (JIRA)" <ji...@apache.org> on 2010/11/29 11:38:38 UTC
[jira] Closed: (LUCENE-2783) Deadlock in IndexWriter
[ https://issues.apache.org/jira/browse/LUCENE-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christoph Goller closed LUCENE-2783.
------------------------------------
Resolution: Fixed
Already fixed with introduction of mergeDone flag in OneMerge of Lucene upcoming 2.9.4
> Deadlock in IndexWriter
> -----------------------
>
> Key: LUCENE-2783
> URL: https://issues.apache.org/jira/browse/LUCENE-2783
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.9.3
> Environment: ALL
> Reporter: Christoph Goller
> Fix For: 2.9.4
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> If autoCommit == true a merge usually triggers a commit. A commit (prepareCommit) can trigger a merge vi the flush method. There is a synchronization mechanism for commit (commitLock) and a separate synchronization mechanism for merging (ConcurrentMergeScheduler.wait). If one thread holds the commitLock monitor and another one holds the ConcurrentMergeScheduler monitor we have a deadlock.
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org