[
https://issues.apache.org/jira/browse/YARN-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe reopened YARN-786:
-----------------------------
Reopening this, as this change causes NPEs in clients. For example:
{noformat}
$ mapred job -list
2013-11-19 16:52:15,590 INFO [main] client.RMProxy
(RMProxy.java:createRMProxy(56)) - Connecting to ResourceManager at x/x:x
Exception in thread "main" java.lang.NullPointerException
at
org.apache.hadoop.mapreduce.TypeConverter.fromYarn(TypeConverter.java:445)
at
org.apache.hadoop.mapreduce.TypeConverter.fromYarnApps(TypeConverter.java:460)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.getAllJobs(ResourceMgrDelegate.java:125)
at org.apache.hadoop.mapred.YARNRunner.getAllJobs(YARNRunner.java:164)
at
org.apache.hadoop.mapreduce.Cluster.getAllJobStatuses(Cluster.java:293)
at org.apache.hadoop.mapreduce.tools.CLI.listJobs(CLI.java:511)
at org.apache.hadoop.mapreduce.tools.CLI.run(CLI.java:319)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.mapred.JobClient.main(JobClient.java:1239)
{noformat}
Prior to this change RMAppAttemptImpl.getApplicationResourceUsageReport() could
not return null, but now it can for any application that has finished. Clients
do not expect a null resource usage report within an application report.
> Expose application resource usage in RM REST API
> ------------------------------------------------
>
> Key: YARN-786
> URL: https://issues.apache.org/jira/browse/YARN-786
> Project: Hadoop YARN
> Issue Type: Improvement
> Affects Versions: 2.0.4-alpha
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Fix For: 2.3.0
>
> Attachments: YARN-786-1.patch, YARN-786-2.patch, YARN-786.patch
>
>
> It might be good to require users to explicitly ask for this information, as
> it's a little more expensive to collect than the other fields in AppInfo.
--
This message was sent by Atlassian JIRA
(v6.1#6144)