[
https://issues.apache.org/jira/browse/TEZ-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13965899#comment-13965899
]
Bikas Saha commented on TEZ-1039:
---------------------------------
IMO, containerId will be part of TaskLocationHint since essentially we are
affinitizing the task to the container and the location hint is the container.
So it will be user visible but it only make sense to access inside the AM -
which would be InputInitializer or VertexManager.
By creating a different object for this we are increasing user API burden (on
which object to create and which API method to call) for the benefit of not
being able to specify container hint via the DAG Api. For that we can make a
check in the DAG api rather than create a new object IMO.
> 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)
