[AMBARI-11754] YARN local usercache is chown'd as user YARN when cluster is in secure mode

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Assignee: Andrew Onischuk
• Reporter: Andrew Onischuk
• Created: 06/Jun/15 13:45
• Updated: 06/Jun/15 16:35
• Resolved: 06/Jun/15 14:02

Description

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¹}

Issue Links

• links to: ReviewBoard