lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-6745) RAMInputStream.clone is not thread safe
Date Tue, 18 Aug 2015 20:45:46 GMT

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

Michael McCandless commented on LUCENE-6745:
--------------------------------------------

bq. Should the test have a shotgun? BTW, I would prefer using ExecutorService for the test.

I prefer to keep concurrency constructs to a minimum ... I think it's important that our tests
are approachable.

And the bug repros fine w/o the shotgun.

> RAMInputStream.clone is not thread safe
> ---------------------------------------
>
>                 Key: LUCENE-6745
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6745
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: Trunk, 5.4
>
>         Attachments: LUCENE-6745.patch
>
>
> This took some time to track down ... it's the root cause of the RangeTree failures that
[~steve_rowe] found at https://issues.apache.org/jira/browse/LUCENE-6697?focusedCommentId=14696999&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14696999
> The problem happens when one thread is using the original IndexInput (RAMInputStream)
from a RAMDirectory, but other threads are also cloning  that IndexInput at the same time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message