[
https://issues.apache.org/jira/browse/MAPREDUCE-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731462#action_12731462
]
Amar Kamat commented on MAPREDUCE-762:
--------------------------------------
Here is a proposal :
# Child jvm, before exiting, should try and cleanup/kill all its sub-processes
# Once a jvm is spawned, its session id should be persisted to task-tracker's
private folder (TaskTracker.SUBDIR/pid with 700 permission?)
# Once the jvm exits, this pid file should be deleted
# Upon restart, the pid files in the private folder should be cleaned up (under
appropriate owner permissions)
# pid files should have sufficient information to reconstruct jvm-context
object which is required by LinuxTaskController to kill the process under user
permission.
@Hemanth, Ravi, Vinod, Sreekanth, Devaraj : Am I missing something here?
> Task's process trees may not be killed if a TT is restarted
> -----------------------------------------------------------
>
> Key: MAPREDUCE-762
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-762
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Reporter: Hemanth Yamijala
>
> Some work has been done to make sure the tasktrackers kill process trees of
> tasks when they finish (either successfully, or with failures or when they
> are killed). Related JIRAs are HADOOP-2721, HADOOP-5488 and HADOOP-5420. But
> when TTs are restarted, we do not handle killing of process trees - though
> tasks will themselves die on re-establishing contact with the TT.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
