Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 30 Oct 2015 00:07:27 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12908847.1446112256000.102683.1446163647799@Atlassian.JIRA>
In-Reply-To: <JIRA.12908847.1446112256000@Atlassian.JIRA>
References: <JIRA.12908847.1446112256000@Atlassian.JIRA>
 <JIRA.12908847.1446112256241@arcas>
Subject: [jira] [Commented] (YARN-4314) Adding container wait time as a
 metric at queue level and application level.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Karthik Kambatla commented on YARN-4314:
----------------------------------------

I was thinking of filing a JIRA for the same. We would like to track allocation latency for each container and roll them up at an app/queue level if possible. I was thinking we could add a timestamp to ResourceRequest and calculate the allocation latency based on that; I am sure it is likely not as simple as that.

> Adding container wait time as a metric at queue level and application level.
> ----------------------------------------------------------------------------
>
>                 Key: YARN-4314
>                 URL: https://issues.apache.org/jira/browse/YARN-4314
>             Project: Hadoop YARN
>          Issue Type: New Feature
>            Reporter: Lavkesh Lahngir
>            Assignee: Lavkesh Lahngir
>
> There is a need for adding the container wait-time which can be tracked at the queue and application level. 
> An application can have two kinds of wait times. One is AM wait time after submission and another is total container wait time between AM asking for containers and getting them. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)