hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HDFS-133) setPermssion locks FSNamesystem across logSync.
Date Wed, 14 Apr 2010 17:32:49 GMT

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

Todd Lipcon resolved HDFS-133.
------------------------------

    Resolution: Duplicate

This fix is covered by HDFS-988

> setPermssion locks FSNamesystem across logSync.
> -----------------------------------------------
>
>                 Key: HDFS-133
>                 URL: https://issues.apache.org/jira/browse/HDFS-133
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Raghu Angadi
>
> {{FSNameSystem.setPermission()}} and other permission related calls lock FSNamesystem
across {{getEditLog().logSync()}} unlike other calls. This increases the negative effect of
slower disk on NameNode. Contrast {code}
>   public synchronized void setPermission(String src, FsPermission permission
>       ) throws IOException {
>     checkOwner(src);
>     dir.setPermission(src, permission);
>     getEditLog().logSync();
>   }{code}and {code}
>   public boolean setReplication(String src, short replication) 
>                                 throws IOException {
>     boolean status = setReplicationInternal(src, replication);
>     getEditLog().logSync();
>     return status;
>   }
> {code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message