hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ray Chiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-5465) Container killed before hprof dumps profile.out
Date Thu, 19 Mar 2015 19:46:40 GMT

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

Ray Chiang commented on MAPREDUCE-5465:
---------------------------------------

I'm still catching up on this JIRA for reviewing, but I do have some questions.

1) I see that SUCCESS_CONTAINER_CLEANUP still exists as a state, but I'm not seeing any transitions
to that state.  Is it still needed?  Or is it a hidden transition now?

2) I see the instantiation of the ExitFinishingOnTimeoutTransition class, but I'm not seeing
it used anywhere.  Along similar lines, I'm not seeing any exit transitions from the SUCCESS_FINISHING_CONTAINER
and FAIL_FINISHING_CONTAINER classes.  I'm also not sure if that is deliberate or not.


> 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
>            Reporter: Radim Kolar
>            Assignee: Ming Ma
>         Attachments: MAPREDUCE-5465-2.patch, MAPREDUCE-5465-3.patch, MAPREDUCE-5465-4.patch,
MAPREDUCE-5465-5.patch, MAPREDUCE-5465-6.patch, MAPREDUCE-5465-7.patch, MAPREDUCE-5465-8.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.3.4#6332)

Mime
View raw message