[
https://issues.apache.org/jira/browse/MAPREDUCE-3240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13137221#comment-13137221
]
Vinod Kumar Vavilapalli commented on MAPREDUCE-3240:
----------------------------------------------------
Just committed the new files which are still lying around in my local workspace.
I just pushed the new files in. Can you try again? Thanks Robert for pointing
out.
> NM should send a SIGKILL for completed containers also
> ------------------------------------------------------
>
> Key: MAPREDUCE-3240
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3240
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, nodemanager
> Affects Versions: 0.23.0
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Hitesh Shah
> Priority: Blocker
> Fix For: 0.23.0
>
> Attachments: MAPREDUCE-3240-20111027.1.txt,
> MAPREDUCE-3240-20111027.2.txt, MR-3240.1.patch, MR-3240.2.patch,
> MR-3240.3.patch, MR-3240.4.wip.patch, MR-3240.5.patch, MR-3240.wip.patch
>
>
> This is to address the containers which exit properly after spawning
> sub-processes themselves. We don't want to leave these sub-process-tree or
> else they can pillage the NM's resources.
> Today, we already have code to send SIGKILL to the whole process-trees
> (because of single sessionId resulting from setsid) when the container is
> alive. We need to obtain the PID of the containers when they start and use
> that PID to send signal for completed containers' case also.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
