[
https://issues.apache.org/jira/browse/TEZ-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004027#comment-14004027
]
Siddharth Seth commented on TEZ-1039:
-------------------------------------
Would be useful to have a comment on if (canMatchWithAffinity), also rename to
canMatchTaskWithAffinity. Is this to delay matching the current task under
consideration, since it is likely to match against an already available
container later in the container loop ?
{code}
if (container.getId().equals(
cookieContainerRequest.getAffinitizedContainer())) {
{code}
The above comment is the reason to not assign firstMatch in the else ?
Otherwise, looks good to me.
> 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, TEZ-1039.3.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)
