[jira] [Comment Edited] (TEZ-1039) Add Container locality to TaskScheduler

["Hitesh Shah (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TEZ-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965878#comment-13965878 ] 

Hitesh Shah edited comment on TEZ-1039 at 4/10/14 9:33 PM:
-----------------------------------------------------------

[~bikassaha] I am assuming that given that VertexLocationHints and TaskLocationHints are user visible classes, location hints used internally that have container hints will be in a separate object not visible as part of the DAG APIs? May be required to be exposed to vertex managers though. 


was (Author: hitesh):
[~bikassaha] I am assuming that given that VertexLocationHints and TaskLocationHints are user visible classes, location hints used internally that container container hints will be in a separate object not visible as part of the DAG APIs? May be required to be exposed to vertex managers though. 

> 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
>
> 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)