[
https://issues.apache.org/jira/browse/MAPREDUCE-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866420#action_12866420
]
Hadoop QA commented on MAPREDUCE-1761:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12444243/MAPREDUCE-1761-v1.1.txt
against trunk revision 943039.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 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 does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/181/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/181/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/181/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-h4.grid.sp2.yahoo.net/181/console
This message is automatically generated.
> FairScheduler should allow separate configuration of node and rack locality
> wait time
> -------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1761
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1761
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.22.0
> Reporter: Scott Chen
> Assignee: Scott Chen
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-1761-v1.1.txt, MAPREDUCE-1761-v1.2.txt,
> MAPREDUCE-1761.txt
>
>
> It would be nice that we can separately assign rack locality wait time.
> In our use case, we would set node locality wait to zero and wait only rack
> locality.
> I propose that we add two parameters
> mapred.fairscheduler.locality.delay.nodetorack
> mapred.fairscheduler.locality.delay.racktoany
> This allows specifying the wait time on each stage.
> And we can use
> mapred.fairscheduler.locality.delay
> as the default value of the above fields so that this is backward compatible.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
