[
https://issues.apache.org/jira/browse/HADOOP-9923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950469#comment-13950469
]
Sanghyun Yun commented on HADOOP-9923:
--------------------------------------
try set users(hdfs, yarn, mapred) to the members of the same group(ex. hadoop)
and change the group of staging dir.
I think this is right usage.
> yarn staging area on hdfs has wrong permission and is created by the wrong
> user
> -------------------------------------------------------------------------------
>
> Key: HADOOP-9923
> URL: https://issues.apache.org/jira/browse/HADOOP-9923
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: André Kelpe
>
> I am setting up a cluster with hadoop 2.1-beta that consists of the following
> components:
> master: runs the namenode, the resourcemanager and the job history server.
> hadoop1, hadoop2, hadoop3: run datanodes and node managers
> I created 3 system users for the different components, like explained in the
> docs:
> hdfs: runs all things hdfs
> yarn: runs all things yarn
> mapred: runs the job history server
> If I now boot up the cluster, I cannot submit jobs since the yarn staging
> area permissions do not allow it.
> What I found out is, that the job-history-server is creating the staging
> directory while starting. This first of all causes it to be owned by the
> wrong user (mapred) and having the wrong permision (770). The docs are not
> really clear if I am supposed to start hdfs first, then create the staging
> area by hand and then start the job-history-server or if this is supposed to
> happen automatically by itself.
> In any case, either the docs should be updated or the job-history-server
> should not create the directory.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
