hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlo Curino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2144) Add logs when preemption occurs
Date Sat, 21 Jun 2014 20:02:25 GMT

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

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

I only skimmed the patch quickly, but I see several places where you are changing method signatures
by adding booleans to communicate the container was preempted. 
Would it be possibly to use/extend some of the container state / event objects that are already
passed around? It might be less intrusive, and if we ever get to different levels of preemption
or anything like that, will also be more flexible of a mechanism.

> 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
>
>
> 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)

Mime
View raw message