You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/06/13 02:33:20 UTC

[jira] [Commented] (TEZ-221) Deadlock in DAGSchedulerMRR when setting slow start to 0.5f on a small cluster

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

Hitesh Shah commented on TEZ-221:
---------------------------------

[~yeshavora] Thanks for reporting the issue. I have updated the jira title to be more clear. 

To clarify for others, based on an offline discussion with [~yeshavora], a job with 80 maps and 10 reduces on a single node cluster hung due to slow start causing the reduces to take up all available resources.
                
> Deadlock in DAGSchedulerMRR when setting slow start to 0.5f on a small cluster
> ------------------------------------------------------------------------------
>
>                 Key: TEZ-221
>                 URL: https://issues.apache.org/jira/browse/TEZ-221
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: yeshavora
>              Labels: TEZ-0.2.0
>
> generate 10GB data using randomwriter and run sort job using tez-mapreduce-example.jar on single node cluster. The job runs very slow. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira