Return-Path: 
 <dev-return-75635-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-dev-archive@www.apache.org
Delivered-To: apmail-ambari-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8CAF7106CA
	for <apmail-ambari-dev-archive@www.apache.org>;
 Sat,  6 Jun 2015 14:03:00 +0000 (UTC)
Received: (qmail 31258 invoked by uid 500); 6 Jun 2015 14:03:00 -0000
Delivered-To: apmail-ambari-dev-archive@ambari.apache.org
Received: (qmail 31216 invoked by uid 500); 6 Jun 2015 14:03:00 -0000
Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ambari.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ambari.apache.org>
List-Post: <mailto:dev@ambari.apache.org>
List-Id: <dev.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list dev@ambari.apache.org
Received: (qmail 31201 invoked by uid 99); 6 Jun 2015 14:03:00 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Jun 2015 14:03:00 +0000
Date: Sat, 6 Jun 2015 14:03:00 +0000 (UTC)
From: "Andrew Onischuk (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12835924.1433598334000.9579.1433599380353@Atlassian.JIRA>
In-Reply-To: <JIRA.12835924.1433598334000@Atlassian.JIRA>
References: <JIRA.12835924.1433598334000@Atlassian.JIRA>
 <JIRA.12835924.1433598334479@arcas>
Subject: [jira] [Resolved] (AMBARI-11754) YARN local usercache is chown'd as
 user YARN when cluster is in secure mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/AMBARI-11754?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Onischuk resolved AMBARI-11754.
--------------------------------------
    Resolution: Fixed

Committed to trunk and branch-2.1

> YARN local usercache is chown'd as user YARN when cluster is in secure mo=
de
> -------------------------------------------------------------------------=
--
>
>                 Key: AMBARI-11754
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11754
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.1.0
>
>
> PROBLEM: When restarting the NodeManager via Ambari, the Ambari agent con=
ducts
> a recursive chown on the YARN local cache configuration directory.
> Something like this: chown -R yarn:hadoop /hadoop/yarn/local
> I have seen this in Ambari 2.0 and Ambari 2.0.1 - where 2.0.1 was upgrade=
d
> from 2.0
> BUSINESS IMPACT: The problem is that user directories exist under
> /hadoop/yarn/local/usercache/<username> and subsequent containers will no=
t
> have rights to the user's directory after the NM restart, in a secure clu=
ster.
> STEPS TO REPRODUCE: N/A
> SUPPORT ANALYSIS: As seen in the Ambari logs for starting the NM:
>    =20
>    =20
>     u"Directory['/hadoop/yarn/local']" {'group': 'hadoop', 'recursive': T=
rue,=20
>     'cd_access': 'a', 'ignore_failures': True, 'mode': 0775, 'owner': 'ya=
rn=C2=B9}=20
>    =20



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