From yarn-issues-return-15066-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Fri Sep 20 20:58:55 2013 Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 85922106B8 for ; Fri, 20 Sep 2013 20:58:55 +0000 (UTC) Received: (qmail 36793 invoked by uid 500); 20 Sep 2013 20:58:54 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 36445 invoked by uid 500); 20 Sep 2013 20:58:54 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 36101 invoked by uid 99); 20 Sep 2013 20:58:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Sep 2013 20:58:54 +0000 Date: Fri, 20 Sep 2013 20:58:54 +0000 (UTC) From: "Andrey Klochkov (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-415) Capture memory utilization at the app-level for chargeback MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773419#comment-13773419 ] Andrey Klochkov commented on YARN-415: -------------------------------------- The proposed implementation uses events fired by the scheduler to track resources usage, so we start ticking as soon as a container is allocated by the scheduler and stop doing that when the container is completed and the scheduler "gets" the resources back. Hence, in case a container fails to start by some reason, we'll stop ticking as soon as RM will get this reported. As for the gap between a container actually finishes and RM gets the report, we don't manage it, i.e. the client will be charged until RM gets the report. Start time and finish time are both computed by the scheduler, i.e. it's on the RM side. Not sure about rounding off - can you point me to the code which does that? I think we just use what's provided in the ApplicationSubmissionContext, i.e. it shouldn't be rounded off. > Capture memory utilization at the app-level for chargeback > ---------------------------------------------------------- > > Key: YARN-415 > URL: https://issues.apache.org/jira/browse/YARN-415 > Project: Hadoop YARN > Issue Type: New Feature > Components: resourcemanager > Affects Versions: 0.23.6 > Reporter: Kendall Thrapp > Assignee: Andrey Klochkov > Attachments: YARN-415--n2.patch, YARN-415--n3.patch, YARN-415.patch > > > For the purpose of chargeback, I'd like to be able to compute the cost of an > application in terms of cluster resource usage. To start out, I'd like to get the memory utilization of an application. The unit should be MB-seconds or something similar and, from a chargeback perspective, the memory amount should be the memory reserved for the application, as even if the app didn't use all that memory, no one else was able to use it. > (reserved ram for container 1 * lifetime of container 1) + (reserved ram for > container 2 * lifetime of container 2) + ... + (reserved ram for container n * lifetime of container n) > It'd be nice to have this at the app level instead of the job level because: > 1. We'd still be able to get memory usage for jobs that crashed (and wouldn't appear on the job history server). > 2. We'd be able to get memory usage for future non-MR jobs (e.g. Storm). > This new metric should be available both through the RM UI and RM Web Services REST API. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira