You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2014/06/16 12:09:02 UTC

[jira] [Updated] (YARN-2144) Add logs when preemption occurs

     [ https://issues.apache.org/jira/browse/YARN-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wangda Tan updated YARN-2144:
-----------------------------

    Attachment: YARN-2144.patch

I’ve attached a patch contains changes to show preemption information on RM app page and RM log,

1) log style:
{code}
2014-06-16 10:45:22,247 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: Non-AM container preempted, appId=appattempt_1402886643897_0002_000001, containerId=container_1402886643897_0002_01_000004
{code}
{code}
2014-06-16 10:45:22,247 INFO org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptImpl: AM container preempted, appId=appattempt_1402886643897_0002_000001, containerId=container_1402886643897_0002_01_000001
{code}

2) Info in app page:
See <AM-page-preemption-info.jpg>

Not Included,
1) Persist preemption info across RM restart/HA.
2) FairScheduler related changes to show preemption info on RM app page is not covered in this patch.

Any feedback is welcome!
Thanks

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