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

lachisis commented on YARN-4382:
--------------------------------

I have tested for the "release_agent" feature, and think it is suitable.
Jun Gong , do you make the patch now?  If not, I will assignee to me and make.

> Container hierarchy in cgroup may remain for ever after the container have be 
> terminated
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-4382
>                 URL: https://issues.apache.org/jira/browse/YARN-4382
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.5.2
>            Reporter: lachisis
>            Assignee: Jun Gong
>
> If we use LinuxContainerExecutor to executor the containers, this question 
> may happens.
> In the common case, when a container run, a corresponding hierarchy will be 
> created in cgroup dir. And when the container terminate, the hierarchy  will 
> be delete in some seconds(this time can be configured by 
> yarn.nodemanager.linux-container-executor.cgroups.delete-delay-ms).
> In the code, I find that, CgroupsLCEResource send a signal to kill container 
> process asynchronously, and in the same time, it will try to delete the 
> container hierarchy  in configured "delete-delay-ms" times. 
> But if the container process be killed for seconds which large than 
> "delete-delay-ms" time, the  container hierarchy  will remain for ever.
>   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to