accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1252) Race condition in BulkImport causes ConcurrentModificationException
Date Mon, 08 Apr 2013 18:17:18 GMT

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

Hudson commented on ACCUMULO-1252:
----------------------------------

Integrated in Accumulo-1.4.x #288 (See [https://builds.apache.org/job/Accumulo-1.4.x/288/])
    ACCUMULO-1252 remove loaded files outside the threadpool (Revision 1465687)

     Result = SUCCESS
ecn : 
Files : 
* /accumulo/branches/1.4/src/server/src/main/java/org/apache/accumulo/server/master/tableOps/BulkImport.java

                
> Race condition in BulkImport causes ConcurrentModificationException
> -------------------------------------------------------------------
>
>                 Key: ACCUMULO-1252
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1252
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>            Reporter: William Slacum
>
> The LoadFiles class gets a synchronized list of files to import and, while iterating
over that list, creates another list of Callable's. If the list of files to load is long enough,
it's possible that a bulk import on a previous file in the list could finish and remove itself
from the master list before all of the commands to import the rest of the files are created.
This causes a ConcurrentModificationException when trying to fetch the next file to load.
> I think the concurrent lists support an iterator that will not fail if the underlying
list is modified, but if not, I think this can be solved by first creating a list of Callables
and then adding them to the thread pool in a separate loop.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message