Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 17 Jun 2014 01:37:02 +0000 (UTC)
From: "Wangda Tan (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12720473.1402440713224.142984.1402969022093@arcas>
In-Reply-To: <JIRA.12720473.1402440713224@arcas>
References: <JIRA.12720473.1402440713224@arcas>
Subject: [jira] [Commented] (YARN-2144) Add logs when preemption occurs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Wangda Tan commented on YARN-2144:
----------------------------------

Hi [~tassapola],
bq. In AM page, Does "Resource Preempted from Current Attempt" mean "Total Resource Preempted from Latest AM attempt"? Can it show only data point from current (is it latest?) attempt?
Yes,
Yes, it can only show data point from current(latest) attempt.
bq. Can you change "#Container Preempted from Current Attempt:" to "Number of Containers Preempted from Current(Latest) Attempt"? # syntax maybe hard to comprehend for wider group of user.
Thanks for this comment, I agree with you. I'll address this comment later.

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