[
https://issues.apache.org/jira/browse/YARN-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982718#comment-14982718
]
Allen Wittenauer 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.
The fact that the RM doesn't keep track of timestamps on containers at all is
particularly annoying when one wants to implement certain types of scheduling
policies (e.g., kill containers that are X old). I think it's inevitable they
are going to be required if not now, later.
> 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)
