[ https://issues.apache.org/jira/browse/HDFS-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059347#comment-13059347 ]
ade commented on HDFS-1257: --------------------------- hi, I believe that I am running into this problem 2 times. > Race condition on FSNamesystem#recentInvalidateSets introduced by HADOOP-5124 > ----------------------------------------------------------------------------- > > Key: HDFS-1257 > URL: https://issues.apache.org/jira/browse/HDFS-1257 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Reporter: Ramkumar Vadali > Assignee: Eric Payne > Attachments: HDFS-1257.patch > > > HADOOP-5124 provided some improvements to FSNamesystem#recentInvalidateSets. > But it introduced unprotected access to the data structure > recentInvalidateSets. Specifically, FSNamesystem.computeInvalidateWork > accesses recentInvalidateSets without read-lock protection. If there is > concurrent activity (like reducing replication on a file) that adds to > recentInvalidateSets, the name-node crashes with a > ConcurrentModificationException. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira