hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6276) Now container kill mechanism may lead process leak
Date Fri, 03 Mar 2017 13:45:45 GMT

    [ 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

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message