hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3981) access time is set without holding writelock in FSNamesystem
Date Mon, 18 Mar 2013 13:02:16 GMT

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

Suresh Srinivas commented on HDFS-3981:

[~teledriver] The direction of this patch looks good. It does not apply to trunk cleanly.
Also can you please add a unit test to catch the related to the change {{now > inode.getAccessTime()
+ getAccessTimePrecision()}}.
> 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, 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,
> 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

View raw message