Hadoop QA commented on YARN-1580:

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

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

    {color:green}+0 tests included{color}.  The patch appears to be a 
documentation patch that doesn't require tests.

    {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/6594//console

This message is automatically generated.

> Documentation error regarding "container-allocation.expiry-interval-ms"
> -----------------------------------------------------------------------
>                 Key: YARN-1580
>                 URL: https://issues.apache.org/jira/browse/YARN-1580
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.2.0
>         Environment: CentOS 6.4
>            Reporter: German Florez-Larrahondo
>            Assignee: Brahma Reddy Battula
>            Priority: Trivial
>             Fix For: 2.7.0
>         Attachments: YARN-1580.patch
> While trying to control settings related to expiration of tokens for long 
> running jobs,based on the documentation ( 
> http://hadoop.apache.org/docs/r2.2.0/hadoop-yarn/hadoop-yarn-common/yarn-default.xml)
>  I attempted to increase values for 
> "yarn.rm.container-allocation.expiry-interval-ms" without luck. Looking code 
> like YarnConfiguration.java I noticed that in  recent versions all these kind 
> of settings now have the prefix "yarn.resourcemanager.rm" as opposed to 
> "yarn.rm". So for this specific case the setting of interest is 
> yarn.resourcemanager.rm.container-allocation.expiry-interval-ms
> I supposed there are other documentation errors similar to this.

This message was sent by Atlassian JIRA

Reply via email to