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] [Updated] (YARN-5001) Aggregated Logs root directory is created with wrong group if nonexistent
Date Tue, 26 Apr 2016 23:02:12 GMT

     [ https://issues.apache.org/jira/browse/YARN-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Haibo Chen updated YARN-5001:
-----------------------------
    Summary: Aggregated Logs root directory is created with wrong group if nonexistent   (was:
Aggregated Logs root directory is created with wrong owner and group if nonexistent )

> 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
>
> Usually, the group owner for /tmp/logs, where the aggregated logs go, is "hadoop". Under
that dir, you then have <username>/logs/<application_id>/<files_per_node>
with group being "hadoop" all the way down. 
> If you delete the /tmp/logs dir (when you want to clean up all the logs), the directory
will be created with a different group "superuser". The JHS runs as the mapred user, who is
a member of the hadoop group. With the new group, the JHS doesn't have permission to read
the logs any more.



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

Mime
View raw message