[ https://issues.apache.org/jira/browse/YARN-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635727#comment-14635727 ]
Bibin A Chundatt commented on YARN-3932: ---------------------------------------- [~leftnoteasy] checkstyle issue is already existing one and test failure are unrelated to this patch. > 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 > Attachments: 0001-YARN-3932.patch, 0002-YARN-3932.patch, > 0003-YARN-3932.patch, 0004-YARN-3932.patch, 0005-YARN-3932.patch, > 0006-YARN-3932.patch, ApplicationReport.jpg, TestResult.jpg > > > 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)