[
https://issues.apache.org/jira/browse/TEZ-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302549#comment-15302549
]
Bikas Saha commented on TEZ-3274:
---------------------------------
There probably isnt. We could use this one. Or if you need an urgent point fix
in this jira some scheduling heuristics could be added optionally to
RootInputInitializer. Though I am not sure what exactly is happening. Since
these tasks also read data from HDFS why would be not want them to start asap
if there is spare capacity. Slow start is effectively also tries to start tasks
as soon as possible (in fact sooner than its inputs are ready so I am not sure
why it was called slow start when it could have been called eager start :) ).
> 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)
