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

Hudson commented on MAPREDUCE-4194:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #2150 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/2150/])
    MAPREDUCE-4194. ConcurrentModificationError in DirectoryCollection 
(Jonathan Eagles via bobby) (Revision 1330552)

     Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1330552
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/DirectoryCollection.java
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestDirectoryCollection.java

                
> ConcurrentModificationError in DirectoryCollection
> --------------------------------------------------
>
>                 Key: MAPREDUCE-4194
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4194
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.3, 2.0.0
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>             Fix For: 0.23.3, 2.0.0, 3.0.0
>
>         Attachments: MAPREDUCE-4194.patch, MAPREDUCE-4194.patch
>
>
> As found as part of work on MAPREDUCE-4169, it is possible for a 
> ConcurrentModificationException to be thrown upon disk failure. 
> DirectoryCollection hands out its internal list structure that is accessed 
> across multiple threads. Upon disk failure its internal list is modified, 
> invalidating all current iterators to that structure.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to