[
https://issues.apache.org/jira/browse/MAPREDUCE-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866354#action_12866354
]
Matei Zaharia commented on MAPREDUCE-1761:
------------------------------------------
This looks good, but I have some minor suggestions on the naming to make it
less verbose:
* Change the variable names from localityDelayNodeLocal and
localityDelayRackLocal to nodeLocalityDelay and rackLocalityDelay.
* Change the config params to mapred.fairscheduler.locality.delay.node and
mapred.fairscheduler.locality.delay.rack
> 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.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.
