[ https://issues.apache.org/jira/browse/HDFS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625729#comment-13625729 ]
Todd Lipcon commented on HDFS-3981: ----------------------------------- Failed test looks like HDFS-3267 (unrelated). I'll commit this momentarily. > access time is set without holding FSNamesystem write lock > ---------------------------------------------------------- > > Key: HDFS-3981 > URL: https://issues.apache.org/jira/browse/HDFS-3981 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 0.23.3, 2.0.3-alpha, 0.23.5 > Reporter: Xiaobo Peng > Assignee: Xiaobo Peng > Attachments: HDFS-3981-branch-0.23.4.patch, > HDFS-3981-branch-0.23.patch, HDFS-3981-branch-2.patch, HDFS-3981-trunk.patch, > hdfs-3981.txt > > > Incorrect condition in {{FSNamesystem.getBlockLocatoins()}} can lead to > updating times without write lock. In most cases this condition will force > {{FSNamesystem.getBlockLocatoins()}} to hold write lock, even if times do not > need to be updated. -- 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