hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1401) With zero sleep-delay-before-sigkill.ms, no signal is ever sent
Date Tue, 12 Nov 2013 02:48:18 GMT

    [ 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 
  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
                        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

View raw message