hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Haibo Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5001) Aggregated Logs root directory is created with wrong group if nonexistent
Date Thu, 05 May 2016 19:24:12 GMT

    [ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272908#comment-15272908

Haibo Chen commented on YARN-5001:

The fix will explicitly set the group of /tmp/logs to the group that the user Node Manager
is running as belongs to. This will not work if the group of the user JHS is running as is
not the same as that of Node Manager. 

> Aggregated Logs root directory is created with wrong group if nonexistent 
> --------------------------------------------------------------------------
>                 Key: YARN-5001
>                 URL: https://issues.apache.org/jira/browse/YARN-5001
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.7.0
>            Reporter: Haibo Chen
>            Assignee: Haibo Chen
>         Attachments: yarn5001.001.patch
> The directory /tmp/logs, where the aggregated logs go, is supposed to be read by JHS.
But if it is not created beforehand, it will be created by NodeManager with the group being
the superuser set in HDFS.  Files created under this directory will then inherit the supergroup
as their groups. This leads to JHS to fail to read the container logs files under that directory
if JHS is not running as a user that belongs to superuser.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message