You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Bibin A Chundatt (JIRA)" <ji...@apache.org> on 2015/07/16 18:53:05 UTC
[jira] [Created] (YARN-3932)
SchedulerApplicationAttempt#getResourceUsageReport should be based on
NodeLabel
Bibin A Chundatt created YARN-3932:
--------------------------------------
Summary: SchedulerApplicationAttempt#getResourceUsageReport should be based on NodeLabel
Key: YARN-3932
URL: https://issues.apache.org/jira/browse/YARN-3932
Project: Hadoop YARN
Issue Type: Bug
Components: resourcemanager
Reporter: Bibin A Chundatt
Assignee: Bibin A Chundatt
Application Resource Report shown wrong when node Label is used.
1.Submit application with NodeLabel
2.Check RM UI for resources used
Allocated CPU VCores and Allocated Memory MB is always {{zero}}
{code}
public synchronized ApplicationResourceUsageReport getResourceUsageReport() {
AggregateAppResourceUsage runningResourceUsage =
getRunningAggregateAppResourceUsage();
Resource usedResourceClone =
Resources.clone(attemptResourceUsage.getUsed());
Resource reservedResourceClone =
Resources.clone(attemptResourceUsage.getReserved());
return ApplicationResourceUsageReport.newInstance(liveContainers.size(),
reservedContainers.size(), usedResourceClone, reservedResourceClone,
Resources.add(usedResourceClone, reservedResourceClone),
runningResourceUsage.getMemorySeconds(),
runningResourceUsage.getVcoreSeconds());
}
{code}
should be {{attemptResourceUsage.getUsed(label)}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)