[ 
https://issues.apache.org/jira/browse/MAPREDUCE-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096731#comment-13096731
 ] 

Hadoop QA commented on MAPREDUCE-2640:
--------------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12492918/MAPREDUCE-2640.r1.diff
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 6 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    -1 findbugs.  The patch appears to introduce 8 new Findbugs (version 1.3.9) 
warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed unit tests in hadoop-mapreduce-project.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-api.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-nodemanager.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-app.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-core.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-hs.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-shuffle.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-client-jobclient.html
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/600//console

This message is automatically generated.

> The maxRunningTasks property of the LimitTasksPerJob scheduler is ambiguous 
> in its description, and must be updated
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2640
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2640
>             Project: Hadoop Map/Reduce
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 0.20.2
>            Reporter: Harsh J
>            Assignee: Harsh J
>              Labels: doc
>             Fix For: 0.23.0
>
>         Attachments: 0.22-MAPREDUCE-2640.r1.diff, 
> 0.23-MAPREDUCE-2640.r1.diff, MAPREDUCE-2640.r1.diff
>
>
> The property's entry in mapred-default.xml is like so:
> {code}
> <property>
>   <name>mapreduce.jobtracker.taskscheduler.maxrunningtasks.perjob</name>
>   <value></value>
>   <description>The maximum number of running tasks for a job before
>   it gets preempted. No limits if undefined.
>   </description>
> </property>
> {code}
> There is no mention that this is a property exclusive to the LimitTasksPerJob 
> scheduler alone. The doc ought to be updated to note that unless there's a 
> plan of reusing such a property (I do not see fair or capacity schedulers 
> utilizing this, and they use their own configs).

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to