[ 
https://issues.apache.org/jira/browse/AMBARI-17633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15409947#comment-15409947
 ] 

Hudson commented on AMBARI-17633:
---------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #5466 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5466/])
AMBARI-17633: yarn.nodemanager.remote-app-log-dir should be added (jluniya: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=caa2d3e225881e9fdab82a234afb6f7a21eadd28])
* ambari-server/src/test/python/stacks/2.0.6/YARN/test_historyserver.py
* 
ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py


> yarn.nodemanager.remote-app-log-dir should be added stickybit.
> --------------------------------------------------------------
>
>                 Key: AMBARI-17633
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17633
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>         Environment: CentOS7.2 Ambari2.4, HDP2.4
>            Reporter: Masahiro Tanaka
>            Assignee: Masahiro Tanaka
>             Fix For: trunk
>
>         Attachments: AMBARI-17633.1.patch, AMBARI-17633.2.patch, 
> AMBARI-17633.patch
>
>
> When installing YARN+MapReduce2, I got a WARN message in nodemanager log(in 
> Log Search View) like below
> {code}
> 2016-07-09 06:30:21,865 WARN logaggregation.LogAggregationService 
> LogAggregationService.java:230 - Remote Root Log Dir [/app-logs] already 
> exist, but with incorrect permissions. Expected: [rwxrwxrwt], Found: 
> [rwxrwxrwx]. The cluster may have problems with multiple users. 
> {code}
> I think the cause of this WARN is 
> [this](https://github.com/apache/ambari/blob/trunk/ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/package/scripts/yarn.py#L115).
> We should add stickybit to {{yarn.nodemanager.remote-app-log-dir}}.



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

Reply via email to