[
https://issues.apache.org/jira/browse/YARN-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14990346#comment-14990346
]
Karthik Kambatla commented on YARN-4314:
----------------------------------------
bq. I feel adding timestamp to each resource request will be costly and all the
existing applications will need to migrate to use this metric.
I was not suggesting the AM set it. It might not be a bad idea to let the AMs
set it optionally.
I was thinking the RM could set this on receiving a ResourceRequest, and use it
to determine duration.
> 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)
