[
https://issues.apache.org/jira/browse/TEZ-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300290#comment-15300290
]
Jonathan Eagles commented on TEZ-3274:
--------------------------------------
Looking at it more in detail, MRInput has an input initializer that forces the
use of RootInputVertexManager. The VertexImpl.assignVertexManager holds the
logic to choose vertex manager.
The MRInput has an initializer related to split calculation. Does MRInput
always require an input initializer in all cases? Can the slow start capability
be added to the RootInputVertexManager?
> Vertex with MRInput and shuffle input does not respect slow start
> -----------------------------------------------------------------
>
> Key: TEZ-3274
> URL: https://issues.apache.org/jira/browse/TEZ-3274
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jonathan Eagles
>
> Vertices with shuffle input and MRInput choose RootInputVertexManager (and
> not ShuffleVertexManager) and start containers and tasks immediately. In this
> scenario, resources can be wasted since they do not respect
> tez.shuffle-vertex-manager.min-src-fraction
> tez.shuffle-vertex-manager.max-src-fraction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
