[
https://issues.apache.org/jira/browse/YARN-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391687#comment-16391687
]
Wangda Tan commented on YARN-4488:
----------------------------------
[~ywskycn], apologize that I missed your ping in YARN-7844. I think it will be
useful to understand the latency between resource requested added and container
allocated. However, as I commented above:
https://issues.apache.org/jira/browse/YARN-4488?focusedCommentId=16382744&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16382744,
it could be an expensive call to record a more accurate delay. IMHO, if we
don't record accurate delay, the metrics will not be useful.
So my personal suggestion is: can we check if it is possible to put the
container allocation delay code to a isolated module, and enable only on demand
(just like the approach of YARN-7844). [[email protected]], does it make
sense to you? Could you investigate this option?
> CapacityScheduler: Compute per-container allocation latency and roll up to
> get per-application and per-queue
> ------------------------------------------------------------------------------------------------------------
>
> Key: YARN-4488
> URL: https://issues.apache.org/jira/browse/YARN-4488
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Karthik Kambatla
> Assignee: Manikandan R
> Priority: Major
> Attachments: YARN-4485.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
