Apache
/
hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HDFS-9415. Document dfs.cluster.administrators and dfs.permissions.superusergroup. (Contributed by Xiaobing Zhou)

This commit is contained in:
Arpit Agarwal 2016-01-14 14:17:52 -08:00
parent 817cc1f02a
commit e97cd4ade5
2 changed files with 16 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
View File

@ -1813,6 +1813,9 @@ Release 2.8.0 - UNRELEASED
HDFS-9630. DistCp minor refactoring and clean up. (Kai Zheng via zhz)
HDFS-9415. Document dfs.cluster.administrators and
dfs.permissions.superusergroup. (Xiaobing Zhou via Arpit Agarwal)
OPTIMIZATIONS
HDFS-8026. Trace FSOutputSummer#writeChecksumChunks rather than

19
hadoop-hdfs-project/hadoop-hdfs/src/main/resources/hdfs-default.xml
View File

@ -414,17 +414,24 @@
<property>
<name>dfs.permissions.superusergroup</name>
<value>supergroup</value>
<description>The name of the group of super-users.</description>
<description>The name of the group of super-users.
The value should be a single group name.
</description>
</property>
<!--
<property>
<name>dfs.cluster.administrators</name>
<value>ACL for the admins</value>
<description>This configuration is used to control who can access the
default servlets in the namenode, etc.
<value></value>
<description>ACL for the admins, this configuration is used to control
who can access the default servlets in the namenode, etc. The value
should be a comma separated list of users and groups. The user list
comes first and is separated by a space followed by the group list,
e.g. "user1,user2 group1,group2". Both users and groups are optional,
so "user1", " group1", "", "user1 group1", "user1,user2 group1,group2"
are all valid (note the leading space in " group1"). '*' grants access
to all users and groups, e.g. '*', '* ' and ' *' are all valid.
</description>
</property>
-->
<property>
<name>dfs.namenode.acls.enabled</name>