hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2144) Add logs when preemption occurs
Date Tue, 17 Jun 2014 02:03:02 GMT

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

Wangda Tan commented on YARN-2144:

bq. Haven't looked at the patch. YARN-1809 is adding the attempt UI, Maybe the app UI should
show the total preempted containers info, and attempt UI should show each attempt's preempted
containers info?
Thanks for pointing the attempt UI JIRA. I think RM will cleanup application's resource usage
at the beginning of each attempt start, so it should make sense to show latest attempt's preempted
containers info on app UI. 
And after we can persist preemption info across RM restart and YARN-1807 committed, we can
show each attempt's preempted containers info on attempts UI.
Do you agree?

> 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
> There should be easy-to-read logs when preemption does occur. 
> 1. For debugging purpose, RM should log this.
> 2. For administrative purpose, RM webpage should have a page to show recent preemption
> 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

View raw message