[
https://issues.apache.org/jira/browse/YARN-4287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012380#comment-15012380
]
Hudson commented on YARN-4287:
------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #1420 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/1420/])
move fix version of YARN-4287 from 2.8.0 to 2.7.3 (wangda: rev
23a130abd7f26ca95d7e94988c7bc45c6d419d0f)
* hadoop-yarn-project/CHANGES.txt
> Capacity Scheduler: Rack Locality improvement
> ---------------------------------------------
>
> Key: YARN-4287
> URL: https://issues.apache.org/jira/browse/YARN-4287
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: capacityscheduler
> Affects Versions: 2.7.1
> Reporter: Nathan Roberts
> Assignee: Nathan Roberts
> Fix For: 2.8.0
>
> Attachments: YARN-4287-minimal-v2.patch, YARN-4287-minimal-v3.patch,
> YARN-4287-minimal-v4-branch-2.7.patch, YARN-4287-minimal-v4.patch,
> YARN-4287-minimal.patch, YARN-4287-v2.patch, YARN-4287-v3.patch,
> YARN-4287-v4.patch, YARN-4287.patch
>
>
> YARN-4189 does an excellent job describing the issues with the current delay
> scheduling algorithms within the capacity scheduler. The design proposal also
> seems like a good direction.
> This jira proposes a simple interim solution to the key issue we've been
> experiencing on a regular basis:
> - rackLocal assignments trickle out due to nodeLocalityDelay. This can have
> significant impact on things like CombineFileInputFormat which targets very
> specific nodes in its split calculations.
> I'm not sure when YARN-4189 will become reality so I thought a simple interim
> patch might make sense. The basic idea is simple:
> 1) Separate delays for rackLocal, and OffSwitch (today there is only 1)
> 2) When we're getting rackLocal assignments, subsequent rackLocal assignments
> should not be delayed
> Patch will be uploaded shortly. No big deal if the consensus is to go
> straight to YARN-4189.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
