ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-11754) YARN local usercache is chown'd as user YARN when cluster is in secure mode
Date Sat, 06 Jun 2015 14:03:00 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-11754?page=com.atlassian.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 mode
> ---------------------------------------------------------------------------
>
>                 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 conducts
> 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 upgraded
> from 2.0
> BUSINESS IMPACT: The problem is that user directories exist under
> /hadoop/yarn/local/usercache/<username> and subsequent containers will not
> have rights to the user's directory after the NM restart, in a secure cluster.
> STEPS TO REPRODUCE: N/A
> SUPPORT ANALYSIS: As seen in the Ambari logs for starting the NM:
>     
>     
>     u"Directory['/hadoop/yarn/local']" {'group': 'hadoop', 'recursive': True, 
>     'cd_access': 'a', 'ignore_failures': True, 'mode': 0775, 'owner': 'yarn┬╣} 
>     



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

Mime
View raw message