Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 3 Mar 2014 16:35:22 +0000 (UTC)
From: "Ming Ma (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12635029.1362324362404.3555.1393864522078@arcas>
In-Reply-To: <JIRA.12635029.1362324362404@arcas>
References: <JIRA.12635029.1362324362404@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5465) Container killed before hprof
 dumps profile.out
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-5465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ming Ma updated MAPREDUCE-5465:
-------------------------------

    Affects Version/s:     (was: 2.0.3-alpha)
                       trunk
               Status: Patch Available  (was: Open)

> Container killed before hprof dumps profile.out
> -----------------------------------------------
>
>                 Key: MAPREDUCE-5465
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5465
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am, mrv2
>    Affects Versions: trunk
>            Reporter: Radim Kolar
>            Assignee: Ming Ma
>         Attachments: MAPREDUCE-5465-2.patch, MAPREDUCE-5465.patch
>
>
> If there is profiling enabled for mapper or reducer then hprof dumps profile.out at process exit. It is dumped after task signaled to AM that work is finished.
> AM kills container with finished work without waiting for hprof to finish dumps. If hprof is dumping larger outputs (such as with depth=4 while depth=3 works) , it could not finish dump in time before being killed making entire dump unusable because cpu and heap stats are missing.
> There needs to be better delay before container is killed if profiling is enabled.


--
This message was sent by Atlassian JIRA
(v6.2#6252)