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

Raghu Angadi updated HADOOP-3082:
---------------------------------

    Description: 
{{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}


  was:

{{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}


        Summary: setPermssion locks FSNamesystem across logSync.  (was: 
setPermssion locks FSNamesystem for logSyc.)

> setPermssion locks FSNamesystem across logSync.
> -----------------------------------------------
>
>                 Key: HADOOP-3082
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3082
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.0
>            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.
-
You can reply to this email to add a comment to the issue online.

Reply via email to