[
https://issues.apache.org/jira/browse/YARN-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071181#comment-14071181
]
Wangda Tan commented on YARN-415:
---------------------------------
Hi [~eepayne],
Thanks for your reply, I think following is completely make sense,
bq. RMAppAttempt can access the scheduler via the 'scheduler' variable, but
that is of type YarnScheduler, which does not have all of the interfaces
available that AbstractYarnScheduler has. Are you suggesting that I add the
getMemoryUtilization method to the YarnScheduler interface? Or, are you
suggesting that the RMAppAttempt#scheduler variable be cast-ed to
AbstractYarnScheduler? Or, am I missing the point?
RMAppAttempt should only hold reference to YarnScheduler, we shouldn't change
that behavior, or user may fail when switch to a scheduler doesn't inherit from
AbstractYarnScheduler.
So according to this, I would like to suggest ignore #5, even if
getAppAttemptMetrics may block scheduler thread. We can think about how to
improve this in a future separated task.
Thanks,
Wangda
> Capture memory utilization at the app-level for chargeback
> ----------------------------------------------------------
>
> Key: YARN-415
> URL: https://issues.apache.org/jira/browse/YARN-415
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: resourcemanager
> Affects Versions: 0.23.6
> Reporter: Kendall Thrapp
> Assignee: Andrey Klochkov
> Attachments: YARN-415--n10.patch, YARN-415--n2.patch,
> YARN-415--n3.patch, YARN-415--n4.patch, YARN-415--n5.patch,
> YARN-415--n6.patch, YARN-415--n7.patch, YARN-415--n8.patch,
> YARN-415--n9.patch, YARN-415.201405311749.txt, YARN-415.201406031616.txt,
> YARN-415.201406262136.txt, YARN-415.201407042037.txt,
> YARN-415.201407071542.txt, YARN-415.201407171553.txt,
> YARN-415.201407172144.txt, YARN-415.patch
>
>
> For the purpose of chargeback, I'd like to be able to compute the cost of an
> application in terms of cluster resource usage. To start out, I'd like to
> get the memory utilization of an application. The unit should be MB-seconds
> or something similar and, from a chargeback perspective, the memory amount
> should be the memory reserved for the application, as even if the app didn't
> use all that memory, no one else was able to use it.
> (reserved ram for container 1 * lifetime of container 1) + (reserved ram for
> container 2 * lifetime of container 2) + ... + (reserved ram for container n
> * lifetime of container n)
> It'd be nice to have this at the app level instead of the job level because:
> 1. We'd still be able to get memory usage for jobs that crashed (and wouldn't
> appear on the job history server).
> 2. We'd be able to get memory usage for future non-MR jobs (e.g. Storm).
> This new metric should be available both through the RM UI and RM Web
> Services REST API.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
