You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Jonathan Eagles (JIRA)" <ji...@apache.org> on 2016/05/25 21:01:13 UTC

[jira] [Comment Edited] (TEZ-3274) Vertex with MRInput and shuffle input does not respect slow start

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

Jonathan Eagles edited comment on TEZ-3274 at 5/25/16 9:00 PM:
---------------------------------------------------------------

[~bikassaha] is this issue better addressed under an existing jira? One of the reasons this is important is when comparing Tez to MapReduce, tez jobs with MRInput and shuffle input (for example replicated joins) will show high in some cases.


was (Author: jeagles):
[~bikassaha] is this issue better addressed under an existing jira. One of the reasons this is important is when comparing Tez to MapReduce, tez jobs with mrinput and shuffle input (for example replicated joins) will show high in some cases.

> 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)