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

Posted to issues@tez.apache.org by "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/11/20 03:00:19 UTC

[jira] [Resolved] (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:all-tabpanel ]

Bikas Saha resolved TEZ-221.
----------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0

commit 808be4d0476eea14114096953dd46b06a8d74233
Author: Bikas Saha <bi...@apache.org>
Date:   Tue Nov 19 17:55:25 2013 -0800

    TEZ-221. Deadlock in DAGSchedulerMRR when setting slow start to 0.5f on a small cluster (bikas)

> 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: Yesha Vora
>            Assignee: Bikas Saha
>              Labels: TEZ-0.2.0
>             Fix For: 0.2.0
>
>         Attachments: TEZ-221.1.patch, TEZ-221.2.patch, TEZ-221.3.patch, TEZ-221.4.preemption.patch, TEZ-221.5.patch, TEZ-221.6.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)