[
https://issues.apache.org/jira/browse/HDFS-3981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13597834#comment-13597834
]
Xiaobo Peng commented on HDFS-3981:
-----------------------------------
Attached the patches for trunk, branch-2 and 0.23.
Note: my previous comment "Also, seems we need to release readlock before
trying to acquire writelock..." is invalid.
> access time is set without holding writelock in FSNamesystem
> ------------------------------------------------------------
>
> 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
> Reporter: Xiaobo Peng
> Assignee: Xiaobo Peng
> Priority: Minor
> Attachments: HDFS-3981-branch-0.23.4.patch,
> HDFS-3981-branch-0.23.patch, HDFS-3981-branch-2.patch, HDFS-3981-trunk.patch
>
>
> 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
