You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2008/03/24 19:21:24 UTC
[jira] Created: (HADOOP-3082) setPermssion locks FSNamesystem for
logSyc.
setPermssion locks FSNamesystem for logSyc.
-------------------------------------------
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.
[jira] Updated: (HADOOP-3082) setPermssion locks FSNamesystem
across logSync.
Posted by "Robert Chansler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-3082:
------------------------------------
Fix Version/s: (was: 0.17.0)
> 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.
[jira] Updated: (HADOOP-3082) setPermssion locks FSNamesystem
across logSync.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-3082) setPermssion locks FSNamesystem
across logSync.
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raghu Angadi updated HADOOP-3082:
---------------------------------
Fix Version/s: 0.17.0
> 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
> Fix For: 0.17.0
>
>
> {{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.