lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Updated: (LUCENE-2730) intermittent deadlock in TestAtomicUpdate,TestIndexWriterExceptions
Date Sat, 30 Oct 2010 14:30:19 GMT


Michael McCandless updated LUCENE-2730:

    Attachment: LUCENE-2730.patch

Attached patch.

The deadlock in TestIndexWriterExceptions was due to locks being acquired in the wrong order;
to fix this I've removed synchronized from TestHash.abort.  DocumentsWriter idles all other
threads before calling abort so we don't need to sync.  I'll also remove this from trunk and

TestAtomicUpdate's deadlock only happens when autoCommit=true, when one thread has called
commit and the flush by that commit tries to spawn new merges, which enters CMS who then hits
the max merge thread count and waits for merge threads to finish while another merge thread
is attempting an autoCommit.  I don't think we need to make any changes to 3.x/trunk for this
(autoCommit is gone).

> intermittent deadlock in TestAtomicUpdate,TestIndexWriterExceptions
> -------------------------------------------------------------------
>                 Key: LUCENE-2730
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.9.3, 3.0.2
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 2.9.4, 3.0.3
>         Attachments: LUCENE-2730.patch
> While backporting issues for 2.9.x/3.0.x release I hit deadlocks in these two tests,
under both test-core and test-tag.

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:
For additional commands, e-mail:

View raw message