hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaobo Peng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3981) access time is set without holding writelock in FSNamesystem
Date Thu, 27 Sep 2012 20:25:08 GMT

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

Xiaobo Peng commented on HDFS-3981:
-----------------------------------

Thank you, Konstantin. I will follow your suggestions and create a patch for 0.23.4
                
> 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: name-node
>    Affects Versions: 0.23.3
>            Reporter: Xiaobo Peng
>            Assignee: Xiaobo Peng
>            Priority: Minor
>
> 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

Mime
View raw message