hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5465) Container killed before hprof dumps profile.out
Date Mon, 28 Oct 2013 16:40:39 GMT

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

Ravi Prakash commented on MAPREDUCE-5465:
-----------------------------------------

And I totally forgot to answer Hitesh's question! Sorry about that. :( NM_SLEEP_DELAY_BEFORE_SIGKILL_MS
handles the timeout before a SIGKILL. However at that point in time, a SIGTERM has already
been sent once. This can be disruptive too.

> 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: 2.0.3-alpha
>            Reporter: Radim Kolar
>            Assignee: Ravi Prakash
>         Attachments: 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.1#6144)

Mime
View raw message