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

Daniel Templeton commented on YARN-6208:
----------------------------------------

It's not like the log message is going to appear so often that we need to worry 
about optimizing for length.  I much prefer having a log message that can be 
understood without looking at source code.

> Improve the log when FinishAppEvent sent to the NodeManager which didn't run 
> the application
> --------------------------------------------------------------------------------------------
>
>                 Key: YARN-6208
>                 URL: https://issues.apache.org/jira/browse/YARN-6208
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Akira Ajisaka
>            Assignee: Akira Ajisaka
>            Priority: Minor
>              Labels: newbie, supportability
>         Attachments: YARN-6208.01.patch
>
>
> When FinishAppEvent of an application is sent to a NodeManager and there are 
> no applications of the application ran on the NodeManager, we can see the 
> following log:
> {code}
> 2015-12-28 11:59:18,725 WARN 
> org.apache.hadoop.yarn.server.nodemanager.containermanager.ContainerManagerImpl:
>  Event EventType: FINISH_APPLICATION sent to absent application 
> application_1446103803043_9892
> {code}
> YARN-4520 made the log as follows:
> {code}
>           LOG.warn("couldn't find application " + appID + " while processing"
>               + " FINISH_APPS event");
> {code}
> and I'm thinking it can be improved.
> * Make the log WARN from INFO
> * Add why the NodeManager couldn't find the application. For example, 
> "because there were no containers of the application ran on the NodeManager."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to