[
https://issues.apache.org/jira/browse/YARN-2868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520196#comment-14520196
]
Vinod Kumar Vavilapalli commented on YARN-2868:
-----------------------------------------------
Going through old tickets. I have two questions
# Why was this done in a scheduler specific way? RMAppAttempt clearly knows
when it requests and when it gets the allocation.
# Seems like the patch only looks at the first AM container. What happens if
the we have a 2nd AM container?
I accidentally closed this ticket, so doesn't look like I can reopen it. If
folks agree, I will open a new ticket.
> FairScheduler: Metric for latency to allocate first container for an
> application
> --------------------------------------------------------------------------------
>
> Key: YARN-2868
> URL: https://issues.apache.org/jira/browse/YARN-2868
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Ray Chiang
> Assignee: Ray Chiang
> Labels: metrics, supportability
> Fix For: 2.8.0
>
> Attachments: YARN-2868-01.patch, YARN-2868.002.patch,
> YARN-2868.003.patch, YARN-2868.004.patch, YARN-2868.005.patch,
> YARN-2868.006.patch, YARN-2868.007.patch, YARN-2868.008.patch,
> YARN-2868.009.patch, YARN-2868.010.patch, YARN-2868.011.patch,
> YARN-2868.012.patch
>
>
> Add a metric to measure the latency between "starting container allocation"
> and "first container actually allocated".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
