You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/11/12 03:48:18 UTC

[jira] [Commented] (YARN-1401) With zero sleep-delay-before-sigkill.ms, no signal is ever sent

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

Hadoop QA commented on YARN-1401:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12613291/YARN-401.v01.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/2420//console

This message is automatically generated.

> With zero sleep-delay-before-sigkill.ms, no signal is ever sent
> ---------------------------------------------------------------
>
>                 Key: YARN-1401
>                 URL: https://issues.apache.org/jira/browse/YARN-1401
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.2.0
>            Reporter: Gera Shegalov
>         Attachments: YARN-401.v01.patch
>
>
> If you set in yarn-site.xml yarn.nodemanager.sleep-delay-before-sigkill.ms=0 then an unresponsive child JVM is never killed. In MRv1, TT used to immediately SIGKILL in this case. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)