Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CE590186C2 for ; Mon, 27 Jul 2015 04:10:40 +0000 (UTC) Received: (qmail 8242 invoked by uid 500); 27 Jul 2015 04:10:32 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 8150 invoked by uid 500); 27 Jul 2015 04:10:31 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 8140 invoked by uid 99); 27 Jul 2015 04:10:31 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jul 2015 04:10:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3ED8C1A7928 for ; Mon, 27 Jul 2015 04:10:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ZWROVL6_b3bz for ; Mon, 27 Jul 2015 04:10:25 +0000 (UTC) Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 04D3043CD4 for ; Mon, 27 Jul 2015 04:10:25 +0000 (UTC) Received: by igk11 with SMTP id 11so46003977igk.1 for ; Sun, 26 Jul 2015 21:10:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; bh=pjkz2bjwQnqMYEfdODfXyi39+rySeurKViSqWPGd7h8=; b=dFMLHqEbe9FPWeoB1FreWd7xyRlAWjPb+6PkFLACZBfHIXUTLOfGF6Pkzfio7G18kE E8ERzRWLRAF0TMiyUNTL5OwGnNm1FoyXgAk0rK+OzsFfv9YCBJIrWMgQd7KNQRrx6qwV 0oayJnhOEqIVAlSk7VsDr692kDk0UF4M2agsoTnvAtFF5H1pCA/SwQeVpmSZenyzquDS c0S/Kwtpkyi7D7hvxQ/8iWndLBNjmhKgEyunyky3cCj7/wlqxlKLGFSFfdE0qXJuGVhG CpOmkFKTo4LikroWpYuPwv5rOv7zVfyk5V65stqb/oUzcdW2HETlKFPDZsELE8s4iABb +koQ== X-Gm-Message-State: ALoCoQkbAva4dN5Rmp6r8j6yl4Beu6NhsC25dShPmh2bIlMnWdxNYtDvkOnRU7hq4bRzF/3nvYqj X-Received: by 10.107.10.96 with SMTP id u93mr37774391ioi.172.1437970218228; Sun, 26 Jul 2015 21:10:18 -0700 (PDT) MIME-Version: 1.0 References: <2125876D8382E34C9258B5B906E4EF5C32403B6D@chgpmaldag01wv.bcbsa.com> <2125876D8382E34C9258B5B906E4EF5C32403CA5@chgpmaldag01wv.bcbsa.com> In-Reply-To: <2125876D8382E34C9258B5B906E4EF5C32403CA5@chgpmaldag01wv.bcbsa.com> From: Harsh J Date: Mon, 27 Jul 2015 04:10:08 +0000 Message-ID: Subject: Re: dfs.permissions.superusergroup not working To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a113ee79c0e3d45051bd3885b --001a113ee79c0e3d45051bd3885b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That is correct, that specific property currently accepts only one value. On Mon, Jul 27, 2015 at 8:33 AM Gangavarapu, Venkata < Venkata.Gangavarapu@bcbsa.com> wrote: > Hey Harsh, > > Thanks for responding. > > > > Sorry about that. It was a typo. > > > > It was set as below > > > > > > dfs.permissions.superusergroup > > hdfs,hdpdadmngrp > > > > > > I changed it as below and it is working > > > > > > dfs.permissions.superusergroup > > hdpdadmngrp > > > > > > Looks like it accepts only one group as value. If that=E2=80=99s not true= , please > advise me whar would have went wrong > > > > Thanks, > > Venkat > > > > > > *From:* Harsh J [mailto:harsh@cloudera.com] > *Sent:* Friday, July 24, 2015 9:26 PM > *To:* user@hadoop.apache.org > *Subject:* Re: dfs.permissions.superusergroup not working > > > > Is there a typo in your email, or did you set dfs.cluster.administrators > instead of intending to set dfs.permissions.superusergroup? > > > > Also, are your id outputs from the NameNode machines? Cause by default th= e > group lookups happen local to your NameNode machine. > > > > On Sat, Jul 25, 2015 at 1:31 AM Gangavarapu, Venkata < > Venkata.Gangavarapu@bcbsa.com> wrote: > > Hi, > > > > I have add two groups under dfs.permissions.superusergroup property as > below > > > > dfs.cluster.administrators > > hdfs,hdpdadmngrp > > > > > > Restarted the HDFS after the change. > > > > But I am not able to run the below command > > hdfs dfsadmin =E2=80=93refreshNodes > > > > > > Error says I don=E2=80=99t have privilege to run the above command > > > > My cluster is kerberized. I have principal for my user id. > > > > Hdfs user: > > uid=3D504(hdfs) gid=3D501(hadoop) groups=3D501(hadoop),503(hdfs),506(hdpd= admngrp) > > > > New admin user: > > uid=3D1007(gv07680) gid=3D506(hdpdadmngrp) groups=3D506(hdpdadmngrp) > > > > I am using hadoop-2.6.0 > > > > Please help me with this. > > > > Thanks, > > Venkat > > --001a113ee79c0e3d45051bd3885b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That is correct, that specific property currently accepts = only one value.

On Mon= , Jul 27, 2015 at 8:33 AM Gangavarapu, Venkata <Venkata.Gangavarapu@bcbsa.com> wrote:

Hey Harsh,<= /span>

Thanks for responding.=

=C2=A0

Sorry about that. It was = a typo.

=C2=A0

It was set as below

=C2=A0

<property>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <name> dfs.perm= issions.superusergroup </name>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <value>hdfs,hdp= dadmngrp</value>

=C2=A0=C2=A0=C2=A0 </property>

=C2=A0

I changed it as below and= it is working

=C2=A0

<property>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <name> dfs.perm= issions.superusergroup </name>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <value>hdpdadmn= grp</value>

=C2=A0=C2=A0=C2=A0 </property>

=C2=A0

Looks like it accepts onl= y one group as value. If that=E2=80=99s not true, please advise me whar wou= ld have went wrong

=C2=A0

Thanks,

Venkat

=C2=A0

=C2=A0

From: Harsh J = [mailto:harsh@cloud= era.com]
Sent: Friday, July 24, 2015 9:26 PM
To: user= @hadoop.apache.org
Subject: Re: dfs.permissions.superusergroup not working

=

=C2=A0

Is there a typo in your email, or did you set=C2=A0d= fs.cluster.administrators instead of intending to set dfs.permissions.super= usergroup?

=C2=A0

Also, are your id outputs from the NameNode machines= ? Cause by default the group lookups happen local to your NameNode machine.=

=C2=A0

On Sat, Jul 25, 2015 at 1:31 AM Gangavarapu, Venkata= <Ven= kata.Gangavarapu@bcbsa.com> wrote:

Hi,

=C2=A0

I have add two groups under dfs.permiss= ions.superusergroup property as below

<property>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <name>dfs.clust= er.administrators</name>

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 <value> hdfs,hd= pdadmngrp</value>

=C2=A0=C2=A0=C2=A0 </property>

=C2=A0

Restarted the HDFS after the change.

=C2=A0

But I am not able to run the below command=

hdfs dfsadmin =E2=80=93refreshNodes

=C2=A0

=C2=A0

Error says I don=E2=80=99t have privilege to run the= above command

=C2=A0

My cluster is kerberized. I have principal for my us= er id.

=C2=A0

Hdfs user:

uid=3D504(hdfs) gid=3D501(hadoop) groups=3D501(hadoo= p),503(hdfs),506(hdpdadmngrp)

=C2=A0

New admin user:

uid=3D1007(gv07680) gid=3D506(hdpdadmngrp) groups=3D= 506(hdpdadmngrp)

=C2=A0

I am using hadoop-2.6.0

=C2=A0

Please help me with this.

=C2=A0

Thanks,

Venkat

--001a113ee79c0e3d45051bd3885b--