You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hitesh Shah (JIRA)" <ji...@apache.org> on 2013/03/03 23:25:12 UTC
[jira] [Commented] (YARN-446) Container killed before hprof dumps
profile.out
[ https://issues.apache.org/jira/browse/YARN-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591885#comment-13591885 ]
Hitesh Shah commented on YARN-446:
----------------------------------
Is the just a question of setting YarnConfiguration.NM_SLEEP_DELAY_BEFORE_SIGKILL_MS to a higher value on the cluster that you are testing against?
> Container killed before hprof dumps profile.out
> -----------------------------------------------
>
> Key: YARN-446
> URL: https://issues.apache.org/jira/browse/YARN-446
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client
> Affects Versions: 2.0.3-alpha
> Reporter: Radim Kolar
>
> 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 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