You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2013/08/28 01:19:51 UTC

[jira] [Commented] (HDFS-3981) access time is set without holding FSNamesystem write lock

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

Arpit Agarwal commented on HDFS-3981:
-------------------------------------

Can this be resolved? Thanks.
                
> 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
>             Fix For: 3.0.0, 2.3.0
>
>         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