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] [Updated] (HDFS-4679) Namenode operation checks should be done in a consistent manner
Date Thu, 11 Apr 2013 00:53:19 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Suresh Srinivas updated HDFS-4679:

       Resolution: Fixed
    Fix Version/s: 2.0.5-beta
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

I committed the patch to branch-2 and trunk. Thank you for the review Sanjay and Harsh.
> Namenode operation checks should be done in a consistent manner
> ---------------------------------------------------------------
>                 Key: HDFS-4679
>                 URL: https://issues.apache.org/jira/browse/HDFS-4679
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>             Fix For: 2.0.5-beta
>         Attachments: HDFS-4679.patch, HDFS-4679.patch
> Different operations performs checks in different order. I propose consistently checking
the following in namenode operations:
> # Print debug log related to the operation
> # validate the input parameters, file names
> # Grab read or write lock
> #* check if system is ready for read or write operation
> #* check if system is in safemode (for write operations)
> #* check permissions to see if the user is owner, has access or is super user privileges
> # Release the lock

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