[
https://issues.apache.org/jira/browse/YARN-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823662#comment-13823662
]
Hudson commented on YARN-1401:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1609 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1609/])
YARN-1401. With zero sleep-delay-before-sigkill.ms, no signal is ever sent
(Gera Shegalov via Sandy Ryza) (sandy:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1542038)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/TestContainerLaunch.java
> 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
> Assignee: Gera Shegalov
> Fix For: 2.3.0
>
> Attachments: YARN-1401.v02.patch, 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)
