You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2014/04/08 01:22:14 UTC

[jira] [Commented] (TEZ-1018) VertexManagerPluginContext should enable assigning locality to scheduled tasks

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

Bikas Saha commented on TEZ-1018:
---------------------------------

Based on offline discussion with [~hitesh] we have the following approaches
1) Have API's in the VertexManager context to get the container of a task, get the location of a container and to set the location hint of a new task using one of {container/node/rack}
2) Have API's in the VertexManager to co-locate a task with a different task. This is a more general API that works before any scheduling has begun (and so we dont need to know the real locations) and also works across retries of the attempts. However, we are still not there in terms of support for this in the infrastructure. When we have that then we can add the support by adding task as an option to the location hints defined in 1 above.

> VertexManagerPluginContext should enable assigning locality to scheduled tasks
> ------------------------------------------------------------------------------
>
>                 Key: TEZ-1018
>                 URL: https://issues.apache.org/jira/browse/TEZ-1018
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>
> This may be used by VertexManager to decide the location of their tasks depending on the location of source tasks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)