[jira] [Commented] (YARN-2046) Out of band heartbeats are sent only on container kill and possibly too early

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on YARN-2046:
---------------------------------

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

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

    {color:green}+1 tests included{color}.  The patch appears to include 8 new or modified test files.

      {color:red}-1 javac{color}.  The applied patch generated 1298 javac compiler warnings (more than the trunk's current 1275 warnings).

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:

                  org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesAttempts
                  org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServices
                  org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServices
                  org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServicesAttempts
                  org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServicesTasks
                  org.apache.hadoop.mapreduce.v2.hs.webapp.TestHsWebServicesJobsQuery
                  org.apache.hadoop.mapred.TestMiniMRClientCluster
                  org.apache.hadoop.mapred.TestMiniMRChildTask

                                      The following test timeouts occurred in hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient:

org.apache.hadoopTests
org.apache.hadoop.mapreducTests
org.apache.hadoop.mapreTests
org.apache.haTests
org.apache.hadoop.maTests
org.apache.hadoop.mapreduce.v2.appTests
org.apache.hadoop.mapred.TestMultipleLevelCaching
org.apache.hadoop.mapred.TestReporter
org.apache.hadoop.mapreduce.TestLargeSort

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-YARN-Build/4762//testReport/
Javac warnings: https://builds.apache.org/job/PreCommit-YARN-Build/4762//artifact/trunk/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4762//console

This message is automatically generated.

> Out of band heartbeats are sent only on container kill and possibly too early
> -----------------------------------------------------------------------------
>
>                 Key: YARN-2046
>                 URL: https://issues.apache.org/jira/browse/YARN-2046
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 0.23.10, 2.4.0
>            Reporter: Jason Lowe
>            Assignee: Ming Ma
>         Attachments: YARN-2046.patch
>
>
> [~mingma] pointed out in the review discussion for MAPREDUCE-5465 that the NM is currently sending out of band heartbeats only when stopContainer is called.  In addition those heartbeats might be sent too early because the container kill event is asynchronously posted then the heartbeat monitor is notified.



--
This message was sent by Atlassian JIRA
(v6.2#6252)