[
https://issues.apache.org/jira/browse/YARN-6276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894382#comment-15894382
]
Jason Lowe commented on YARN-6276:
----------------------------------
When the nodemanager kills a container it first sends a SIGTERM to the session
followed shortly afterwards by a SIGKILL. It should not matter what the
process is doing, since if it ignores the SIGTERM then the subsequent SIGKILL
will kill it. Unlike SIGTERM, SIGKILL is not catchable by the receiving
process. Could you elaborate a bit more on how GC activity is involved?
> Now container kill mechanism may lead process leak
> --------------------------------------------------
>
> Key: YARN-6276
> URL: https://issues.apache.org/jira/browse/YARN-6276
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager
> Affects Versions: 3.0.0-alpha2
> Reporter: Feng Yuan
> Assignee: Feng Yuan
>
> When kill bash process, YarnChild may didn`t response because fullgc,
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
