Hadoop QA commented on YARN-3203:

{color:red}-1 overall{color}.  Here are the results of testing the latest 
  against trunk revision ab0b958.

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
                        Also please list what manual steps were performed to 
verify this patch.

    {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 

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

This message is automatically generated.

> Correct the log message #AuxServices.java
> -----------------------------------------
>                 Key: YARN-3203
>                 URL: https://issues.apache.org/jira/browse/YARN-3203
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Brahma Reddy Battula
>            Assignee: Brahma Reddy Battula
>            Priority: Minor
>         Attachments: YARN-3203.patch
>  Currently log is coming like following..
> WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.AuxServices: 
> The Auxilurary Service named 'mapreduce_shuffle' in the configuration is for  
> *{color:red}class class{color}*  org.apache.hadoop.mapred.ShuffleHandler 
> which has a name of 'httpshuffle'. Because these are not the same tools 
> trying to send ServiceData and read Service Meta Data may have issues unless 
> the refer to the name in the config.
> Since get class will return class as prefix,, we no need keep "class" in log..
> {code}
> Class<? extends AuxiliaryService> sClass = conf.getClass(
>               String.format(YarnConfiguration.NM_AUX_SERVICE_FMT, sName), 
> null,
>               AuxiliaryService.class);
> {code}

This message was sent by Atlassian JIRA

Reply via email to