Hadoop QA commented on YARN-2907:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against trunk revision 978736d.

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with 

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/5947//console

This message is automatically generated.

> 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
>         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

Reply via email to