[
https://issues.apache.org/jira/browse/TEZ-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369717#comment-14369717
]
Tsuyoshi Ozawa commented on TEZ-145:
------------------------------------
[~gopalv] [~bikassaha] thank you for the feedback! I have a question about
where to handle the locality. Do you mean that we should use
InputReadyVertexManager? Or, should we create new abstraction layer to deal
with the locality? As a reference, on MAPREDUCE-4502, I changed AppMaster to
handle locality of inputs and when to launch the node-level combiner.
> Support a combiner processor that can run non-local to map/reduce nodes
> -----------------------------------------------------------------------
>
> Key: TEZ-145
> URL: https://issues.apache.org/jira/browse/TEZ-145
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Tsuyoshi Ozawa
> Attachments: TEZ-145.2.patch, WIP-TEZ-145-001.patch
>
>
> For aggregate operators that can benefit by running in multi-level trees,
> support of being able to run a combiner in a non-local mode would allow
> performance efficiencies to be gained by running a combiner at a rack-level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
