You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/12/01 14:42:12 UTC
[jira] [Commented] (YARN-2907) SchedulerNode#toString should print
all resource detail instead of only memory.
[ https://issues.apache.org/jira/browse/YARN-2907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14229792#comment-14229792 ]
Hudson commented on YARN-2907:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #6616 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/6616/])
YARN-2907. SchedulerNode#toString should print all resource detail instead of only memory. (Contributed by Rohith) (junping_du: rev c732ed760e115192652280cd4b5799d49e62db7e)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestWorkPreservingRMRestart.java
* hadoop-yarn-project/CHANGES.txt
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/SchedulerNode.java
> SchedulerNode#toString should print all resource detail instead of only memory.
> -------------------------------------------------------------------------------
>
> Key: YARN-2907
> URL: https://issues.apache.org/jira/browse/YARN-2907
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.6.0
> Reporter: Rohith
> Assignee: Rohith
> Priority: Trivial
> Fix For: 2.7.0
>
> Attachments: 0001-YARN-2907.patch, YARN-2907.1.patch
>
>
> SchedulerNode#toString display only memory. It should display both memory and cpu. It helps while analyzing logs
> {code}
> @Override
> public String toString() {
> return "host: " + rmNode.getNodeAddress() + " #containers="
> + getNumContainers() + " available="
> + getAvailableResource().getMemory() + " used="
> + getUsedResource().getMemory();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)