[
https://issues.apache.org/jira/browse/TEZ-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002578#comment-14002578
]
Siddharth Seth commented on TEZ-1039:
-------------------------------------
[~bikassaha], could you please provide some more insight into why the rack /
non-local checks are required, given that these affinitized requests are being
added with a specific location. The scheduling should be triggered over all
containers soon after adding such a request, and also when a currently running
container becomes free. An example would be helpful.
> Add Container locality to TaskScheduler
> ---------------------------------------
>
> Key: TEZ-1039
> URL: https://issues.apache.org/jira/browse/TEZ-1039
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-1039.1.patch, TEZ-1039.2.patch
>
>
> Currently, the task scheduler support node and rack locality. Proposal is to
> add another level - container locality (given a container) which means first
> try to assign to the container, then fall back to the container's node, rack
> and so on.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
