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

Carlo Curino commented on YARN-2144:
------------------------------------

>From a quick skim, the patch seems fine. As a broader comment (not just about 
>these logs), I think it would be worth looking into more easily parseable 
>logs. We use a rather free form of logs, a bit more structure could go a long 
>way to facilitate debugging.

> Add logs when preemption occurs
> -------------------------------
>
>                 Key: YARN-2144
>                 URL: https://issues.apache.org/jira/browse/YARN-2144
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>    Affects Versions: 2.5.0
>            Reporter: Tassapol Athiapinya
>            Assignee: Wangda Tan
>         Attachments: AM-page-preemption-info.png, YARN-2144.patch, 
> YARN-2144.patch, YARN-2144.patch, YARN-2144.patch, YARN-2144.patch, 
> YARN-2144.patch
>
>
> There should be easy-to-read logs when preemption does occur. 
> RM logs should have following properties:
> * Logs are retrievable when an application is still running and often flushed.
> * Can distinguish between AM container preemption and task container 
> preemption with container ID shown.
> * Should be INFO level log.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to