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/12/09 03:26:09 UTC

[jira] [Commented] (TEZ-644) Failing unit test TestTaskScheduler

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

Bikas Saha commented on TEZ-644:
--------------------------------

A quick note on the memory leak would help. did it go into an infinite loop? this code path should have been executed for the first set of containers at all times with container reuse available. So I wonder how that happened.

> Failing unit test TestTaskScheduler
> -----------------------------------
>
>                 Key: TEZ-644
>                 URL: https://issues.apache.org/jira/browse/TEZ-644
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Hitesh Shah
>            Assignee: Hitesh Shah
>            Priority: Blocker
>             Fix For: 0.3.0
>
>         Attachments: TEZ-644.1.patch, TEZ-644.2.patch
>
>
> Running org.apache.tez.dag.app.rm.TestTaskScheduler
> java.lang.OutOfMemoryError: Java heap space
> Dumping heap to java_pid6502.hprof ...
> Heap dump file created [949324483 bytes in 23.623 secs]



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)