[
https://issues.apache.org/jira/browse/YARN-5112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15292213#comment-15292213
]
Junping Du commented on YARN-5112:
----------------------------------
Thanks [~jianhe] for updating the patch. Remove verifyAndCreateRemoteLogDir()
from initApp() could have two issues:
- YarnRuntimeException could be thrown without proper handling that will crash
LogAggregationService/ContainerManager/NM.
- If root directory is deleted by admin/tools unintentionally, then new
launched apps after the mistaking operation have no chance to fix it.
I think the safe way is tracking down the permission issue and only log for the
first time we hit or the 1st time after permission back to normal for a while.
What do you think?
> Excessive log warnings on NM recovery
> -------------------------------------
>
> Key: YARN-5112
> URL: https://issues.apache.org/jira/browse/YARN-5112
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jian He
> Assignee: Jian He
> Attachments: YARN-5112.2.patch, YARN-5112.patch
>
>
> When there are a lot of apps to recover in NM store, NM prints these two
> lines for each app, which gets annoying.
> {code}
> 2015-10-13 01:58:40,277 WARN logaggregation.LogAggregationService
> (LogAggregationService.java:verifyAndCreateRemoteLogDir(195)) - Remote Root
> Log Dir [/app-logs] already exist, but with incorrect permissions. Expected:
> [rwxrwxrwt], Found: [rwxrwxrwx]. The cluster may have problems with multiple
> users.
> 1111336 2015-10-13 01:58:40,277 WARN logaggregation.AppLogAggregatorImpl
> (AppLogAggregatorImpl.java:<init>(182)) - rollingMonitorInterval is set as
> -1. The log rolling mornitoring interval is disabled. The logs will be
> aggregated after this application is finished.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
