[ 
https://issues.apache.org/jira/browse/HDFS-10863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15512336#comment-15512336
 ] 

www.jbigdata.fr commented on HDFS-10863:
----------------------------------------

Hi,

First of all, I classify this issue as a bug because I didn't know to put "need 
help" in the JIRA.

My env : Ubuntu 16.04, hadoop 2.7.2, 3 DataNode (a DataNode is 2.7.3 I want to 
test "compatibility").

$ uname -a
Linux jbd-vm01 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

$ hadoop version
Hadoop 2.7.2
Subversion https://git-wip-us.apache.org/repos/asf/hadoop.git -r 
b165c4fe8a74265c792ce23f546c64604acf0e41
Compiled by jenkins on 2016-01-26T00:08Z
Compiled with protoc 2.5.0
>From source with checksum d0fda26633fa762bff87ec759ebe689c
This command was run using 
/home/hduser/hadoop-2.7.2/share/hadoop/common/hadoop-common-2.7.2.jar

core-file:
<configuration>
  <property>
    <name>name</name>
    <value>MyDistrib@JBD-2.7.2</value>
  </property>
  <property>
    <name>fs.defaultFS</name>
    <value>hdfs://jbd-vm01.jbdata.fr:9000</value>
  </property>
  <property>
    <name>hadoop.tmp.dir</name>
    <!-- value>/srv/work/hadoop/tmp</value entre les 2, je choisis le moins 
mieux... -->
    <value>/srv/work/hdfs272/tmp</value>
  </property>
  <!-- A quoi sert ce param├ętrage FTP ? Pas une trace dans les LOG -->
  <property>
    <name>fs.ftp.host</name>
    <value>jbd-vm03.jbdata.fr</value>
  </property>
  <property>
    <name>fs.ftp.host.port</name>
    <value>21</value>
  </property>
  <property>
    <name>ha.zookeeper.quorum</name>
    <value>jbd-vm01.jbdata.fr,jbd-vm03.jbdata.fr</value>
  </property>
  <property>
    <name>hadoop.registry.zk.quorum</name>
    <value>jbd-vm01.jbdata.fr:2181,jbd-vm03.jbdata.fr:2181</value>
  </property>
  <property>
    <name>hadoop.http.staticuser.user</name>
    <value>hduser</value>
  </property>
  <!-- NFS gateway -->
  <property>
    <name>hadoop.proxyuser.hduser.groups</name>
    <value>*</value>
  </property>
  <property>
    <name>hadoop.proxyuser.hduser.hosts</name>
    <value>*</value>
  </property>
</configuration>

hdfs-file
<configuration>
  <property>
    <name>dfs.replication</name>
    <!-- value>3</value -->
    <value>2</value>
  </property>
  <property>
    <name>dfs.permissions.superusergroup</name>
    <value>hadoop</value>
  </property>
  <!-- NNx1 -->
  <property>
    <name>dfs.namenode.http-address</name>
    <value>jbd-vm01.jbdata.fr:50070</value>
  </property>
  <property>
    <name>dfs.namenode.https-address</name>
    <value>jbd-vm01.jbdata.fr:50470</value>
  </property>
  <property>
    <name>dfs.namenode.name.dir</name>
    <value>file:/srv/data/hdfs272/nn1,file:/srv/data/hdfs272/nn2</value>
  </property>
  <!-- NN2x1 -->
  <property>
    <name>dfs.namenode.secondary.http-address</name>
    <value>jbd-vm03.jbdata.fr:50090</value>
  </property>
  <property>
    <name>dfs.namenode.secondary.https-address</name>
    <value>jbd-vm03.jbdata.fr:50091</value>
  </property>
  <property>
    <name>dfs.namenode.checkpoint.dir</name>
    <value>file:/srv/data/hdfs272/cp1,file:/srv/data/hdfs272/cp2</value>
  </property>

Need other thing ?

I'm "hard" testing the nfs gateway and I have the same kind of issue with the 
group, but it's maybe another JIRA to open.

$ ll /srv/hdfs_nfs/tmp/zk.tar
-rw-r--r-- 1 hduser 2584148964 41984000 Sep 21 06:01 /srv/hdfs_nfs/tmp/zk.tar

Maybe this issue disapear with the 3.0.0...

> hadoop superusergroup supergroup issue
> --------------------------------------
>
>                 Key: HDFS-10863
>                 URL: https://issues.apache.org/jira/browse/HDFS-10863
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.7.2
>         Environment: $ hadoop version
> Hadoop 2.7.2
>            Reporter: www.jbigdata.fr
>            Priority: Minor
>
> I want to match my unix user to HDFS: hduser:hadoop.
> For the user I use the VE.
> $ echo $HADOOP_HDFS_USER
> hduser
> For the group I use the hdfs-site.xml :
> <property>
>     <name>dfs.permissions.superusergroup</name>
>     <value>hadoop</value>
> </property>
> The namenode log file show the parameter user/group values.
> INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: fsOwner             
> = hduser (auth:SIMPLE)
> INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: supergroup          
> = hadoop
> INFO org.apache.hadoop.hdfs.server.namenode.FSNamesystem: isPermissionEnabled 
> = true
> Everything seems to be OK, but when I copy file form FS to HDFS the group is 
> not correct. It keeps the supergroup default value.
> Thoses shell commands show the issue:
> $ ll /srv/downloads/zk.tar
> -rw-r--r-- 1 hduser hadoop 41984000 Aug 18 13:25 /srv/downloads/zk.tar
> $ hdfs dfs -put /srv/downloads/zk.tar /tmp
> $ hdfs dfs -ls /tmp/zk.tar
> -rw-r--r--   2 hduser supergroup   41984000 2016-09-14 12:47 /tmp/zk.tar
> I have:
> -rw-r--r-- 2 hduser supergroup 41984000 2016-09-14 12:47 /tmp/zk.tar
> I expect :
> -rw-r--r-- 2 hduser hadoop 41984000 2016-09-14 12:47 /tmp/zk.tar
> Why the HDFS group is not the value of the dfs.permissions.superusergroup 
> property ?
> @jbigdata.fr



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to