accumulo-notifications mailing list archives

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


Hudson commented on ACCUMULO-1252:

Integrated in Accumulo-Trunk-Hadoop-2.0 #181 (See [])
    ACCUMULO-1252 remove loaded files outside the threadpool (Revision 1465690)

     Result = SUCCESS
ecn : 
Files : 
* /accumulo/trunk
* /accumulo/trunk/assemble
* /accumulo/trunk/core
* /accumulo/trunk/examples
* /accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/
* /accumulo/trunk/fate/src/main/java/org/apache/accumulo/fate/zookeeper/
* /accumulo/trunk/server
* /accumulo/trunk/server/src/main/java/org/apache/accumulo/server/master/tableOps/
* /accumulo/trunk/src

> Race condition in BulkImport causes ConcurrentModificationException
> -------------------------------------------------------------------
>                 Key: ACCUMULO-1252
>                 URL:
>             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:

View raw message