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, 09 Sep 2013 21:40:53 GMT

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

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

Has any one tried fixing this? If not, I may take a crack it.
                
> 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
>
> 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

Mime
View raw message