[
https://issues.apache.org/jira/browse/YARN-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-2352:
-----------------------------------
Attachment: yarn-2352-3.patch
Thanks Sandy for pointing me to RpcMetrics.
MutableRate seemed a good candidate for the stats that we want to collect.
Updated the patch to use that. For MutableRate, I have enabled showing extended
stats like stdev, min/max etc. by default. In the future, we can add a config
to toggle this if we see any particular overhead.
Regarding using a Singleton, if I don't do this, the tests fail complaining of
already existing metrics for FSDurations. Even QueueMetrics has a static map
that it re-uses.
> FairScheduler: Collect metrics on duration of critical methods that affect
> performance
> --------------------------------------------------------------------------------------
>
> Key: YARN-2352
> URL: https://issues.apache.org/jira/browse/YARN-2352
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: scheduler
> Affects Versions: 2.4.1
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: fs-perf-metrics.png, yarn-2352-1.patch,
> yarn-2352-2.patch, yarn-2352-2.patch, yarn-2352-3.patch
>
>
> We need more metrics for better visibility into FairScheduler performance. At
> the least, we need to do this for (1) handle node events, (2) update, (3)
> compute fairshares, (4) preemption.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
