Hadoop YARN
  1. Hadoop YARN
  2. YARN-101

If the heartbeat message loss, the nodestatus info of complete container will loss too.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.1.0-beta
    • Component/s: nodemanager
    • Labels:
      None
    • Environment:

      suse.

    • Hadoop Flags:
      Reviewed

      Description

      see the red color:

      org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl.java

      protected void startStatusUpdater() {

      new Thread("Node Status Updater") {
      @Override
      @SuppressWarnings("unchecked")
      public void run() {
      int lastHeartBeatID = 0;
      while (!isStopped) {
      // Send heartbeat
      try {
      synchronized (heartbeatMonitor)

      { heartbeatMonitor.wait(heartBeatInterval); }


      // Before we send the heartbeat, we get the NodeStatus,
      // whose method removes completed containers.
      NodeStatus nodeStatus = getNodeStatus();

      nodeStatus.setResponseId(lastHeartBeatID);

      NodeHeartbeatRequest request = recordFactory
      .newRecordInstance(NodeHeartbeatRequest.class);
      request.setNodeStatus(nodeStatus);


      // But if the nodeHeartbeat fails, we've already removed the containers away to know about it. We aren't handling a nodeHeartbeat failure case here.
      HeartbeatResponse response =
      resourceTracker.nodeHeartbeat(request).getHeartbeatResponse();

      if (response.getNodeAction() == NodeAction.SHUTDOWN)

      { LOG .info("Recieved SHUTDOWN signal from Resourcemanager as part of heartbeat," + " hence shutting down."); NodeStatusUpdaterImpl.this.stop(); break; }

      if (response.getNodeAction() == NodeAction.REBOOT)

      { LOG.info("Node is out of sync with ResourceManager," + " hence rebooting."); NodeStatusUpdaterImpl.this.reboot(); break; }

      lastHeartBeatID = response.getResponseId();
      List<ContainerId> containersToCleanup = response
      .getContainersToCleanupList();
      if (containersToCleanup.size() != 0)

      { dispatcher.getEventHandler().handle( new CMgrCompletedContainersEvent(containersToCleanup)); }

      List<ApplicationId> appsToCleanup =
      response.getApplicationsToCleanupList();
      //Only start tracking for keepAlive on FINISH_APP
      trackAppsForKeepAlive(appsToCleanup);
      if (appsToCleanup.size() != 0)

      { dispatcher.getEventHandler().handle( new CMgrCompletedAppsEvent(appsToCleanup)); }

      } catch (Throwable e)

      { // TODO Better error handling. Thread can die with the rest of the // NM still running. LOG.error("Caught exception in status-updater", e); }

      }
      }
      }.start();
      }

      private NodeStatus getNodeStatus() {

      NodeStatus nodeStatus = recordFactory.newRecordInstance(NodeStatus.class);
      nodeStatus.setNodeId(this.nodeId);

      int numActiveContainers = 0;
      List<ContainerStatus> containersStatuses = new ArrayList<ContainerStatus>();
      for (Iterator<Entry<ContainerId, Container>> i =
      this.context.getContainers().entrySet().iterator(); i.hasNext() {
      Entry<ContainerId, Container> e = i.next();
      ContainerId containerId = e.getKey();
      Container container = e.getValue();

      // Clone the container to send it to the RM
      org.apache.hadoop.yarn.api.records.ContainerStatus containerStatus =
      container.cloneAndGetContainerStatus();
      containersStatuses.add(containerStatus);
      ++numActiveContainers;
      LOG.info("Sending out status for container: " + containerStatus);


      // Here is the part that removes the completed containers.
      if (containerStatus.getState() == ContainerState.COMPLETE) {
      // Remove
      i.remove();

      LOG.info("Removed completed container " + containerId);
      }
      }
      nodeStatus.setContainersStatuses(containersStatuses);

      LOG.debug(this.nodeId + " sending out status for "
      + numActiveContainers + " containers");

      NodeHealthStatus nodeHealthStatus = this.context.getNodeHealthStatus();
      nodeHealthStatus.setHealthReport(healthChecker.getHealthReport());
      nodeHealthStatus.setIsNodeHealthy(healthChecker.isHealthy());
      nodeHealthStatus.setLastHealthReportTime(
      healthChecker.getLastHealthReportTime());
      if (LOG.isDebugEnabled())

      { LOG.debug("Node's health-status : " + nodeHealthStatus.getIsNodeHealthy() + ", " + nodeHealthStatus.getHealthReport()); }

      nodeStatus.setNodeHealthStatus(nodeHealthStatus);

      List<ApplicationId> keepAliveAppIds = createKeepAliveApplicationList();
      nodeStatus.setKeepAliveApplications(keepAliveAppIds);

      return nodeStatus;
      }

      1. YARN-101.6.patch
        18 kB
        Xuan Gong
      2. YARN-101.5.patch
        16 kB
        Xuan Gong
      3. YARN-101.4.patch
        16 kB
        Xuan Gong
      4. YARN-101.3.patch
        16 kB
        Xuan Gong
      5. YARN-101.2.patch
        15 kB
        Xuan Gong
      6. YARN-101.1.patch
        3 kB
        Xuan Gong

        Activity

        Hide
        Harsh J added a comment -

        xieguiming - I tweaked the sentences a bit so you're sounding more clear. You're essentially saying that we may be removing completed containers completely, which in case of a node-heartbeat failure, we should make sure to propagate eventually again (on next successful heartbeat), correct?

        Show
        Harsh J added a comment - xieguiming - I tweaked the sentences a bit so you're sounding more clear. You're essentially saying that we may be removing completed containers completely, which in case of a node-heartbeat failure, we should make sure to propagate eventually again (on next successful heartbeat), correct?
        Hide
        Xuan Gong added a comment -

        1. define a field at NodeStatusUpdaterImpl, such as boolean previousHeartBeatProcessed, originally set it as true. Whenever, we catch the exception from ResourceTrackerService, we can set it as false.
        2. define List<ContainerStatus> backUpCompletedContainersStatuses, at function getNodeStatus(), when we find there is any compeletedcontainer, we will remove it as usual and add it to backUpCompletedContainersStatuses to back up, and use it to generate the next containerstatus if previousHeartBeatProcessed is false.
        And at beginning, of course we need to check previousHeartBeatProcessed's value. such as:
        if(previousHeartBeatProcessed)

        {backUpCompletedContainersStatuses.clear()}

        . if previous heartbeat request is processed succesfully by ResourceTrackerService, we can clear the backUpCompletedContainersStatuses list.

        Show
        Xuan Gong added a comment - 1. define a field at NodeStatusUpdaterImpl, such as boolean previousHeartBeatProcessed, originally set it as true. Whenever, we catch the exception from ResourceTrackerService, we can set it as false. 2. define List<ContainerStatus> backUpCompletedContainersStatuses, at function getNodeStatus(), when we find there is any compeletedcontainer, we will remove it as usual and add it to backUpCompletedContainersStatuses to back up, and use it to generate the next containerstatus if previousHeartBeatProcessed is false. And at beginning, of course we need to check previousHeartBeatProcessed's value. such as: if(previousHeartBeatProcessed) {backUpCompletedContainersStatuses.clear()} . if previous heartbeat request is processed succesfully by ResourceTrackerService, we can clear the backUpCompletedContainersStatuses list.
        Hide
        Xuan Gong added a comment -

        1. recreate the patch based on the latest trunk version
        2. add new testcase to test the patch

        Show
        Xuan Gong added a comment - 1. recreate the patch based on the latest trunk version 2. add new testcase to test the patch
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12575611/YARN-101.2.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/611//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/611//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12575611/YARN-101.2.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/611//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/611//console This message is automatically generated.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        Few comments on the patch:

        • previousHeartBeatProcessed can be set back to true only much later, after resourceTracker.nodeHeartbeat(request) returns.
        • backupCompletedContainerStatus doesn't needed to be added to containersStatuses, those containres are already added to the heartbeat-request.
        • Rename previousHeartBeatProcessed to previousHeartBeatSucceeded and backupCompletedContainerStatus to previousContainersStatuses.

        The testcase can be vastly simplified and needs more rigorous validation

        • If the completed container-statuses are validated as part of the custom resource-tracker, most of the spying will be gone
        • Also, we need to populate the container-statuses with a few objects and make sure that lost heart-beats won't lose them.
        Show
        Vinod Kumar Vavilapalli added a comment - Few comments on the patch: previousHeartBeatProcessed can be set back to true only much later, after resourceTracker.nodeHeartbeat(request) returns. backupCompletedContainerStatus doesn't needed to be added to containersStatuses , those containres are already added to the heartbeat-request. Rename previousHeartBeatProcessed to previousHeartBeatSucceeded and backupCompletedContainerStatus to previousContainersStatuses . The testcase can be vastly simplified and needs more rigorous validation If the completed container-statuses are validated as part of the custom resource-tracker, most of the spying will be gone Also, we need to populate the container-statuses with a few objects and make sure that lost heart-beats won't lose them.
        Hide
        Xuan Gong added a comment -

        create the patch based on the latest comments

        Show
        Xuan Gong added a comment - create the patch based on the latest comments
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12575823/YARN-101.3.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        -1 eclipse:eclipse. The patch failed to build with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

        org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer
        org.apache.hadoop.yarn.server.nodemanager.TestNodeStatusUpdater

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/622//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/622//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12575823/YARN-101.3.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. -1 eclipse:eclipse . The patch failed to build with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. -1 core tests . The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager: org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer org.apache.hadoop.yarn.server.nodemanager.TestNodeStatusUpdater +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/622//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/622//console This message is automatically generated.
        Hide
        Xuan Gong added a comment -

        Fix testcase failure

        Show
        Xuan Gong added a comment - Fix testcase failure
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12575989/YARN-101.4.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        -1 eclipse:eclipse. The patch failed to build with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

        org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/626//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/626//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12575989/YARN-101.4.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. -1 eclipse:eclipse . The patch failed to build with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. -1 core tests . The patch failed these unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager: org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/626//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/626//console This message is automatically generated.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        Let's have the test do something like this:

        • In the first heartbeat, report no containers and make it succeed
        • In the second heartbeat, reported two running, two completed and one more running containers in that order. But make the hearbeat fail with an exception
        • In heartbeat #3, report the previous completed containers, add one more running and one more finished container.

        You should control the NM reporting containers by using your custom NMContext and return different container lists on each call to getContainers().

        Also, in the test-case,

        • You can use the newly added YarnServerBuilderUtils for constructing node-heartbeat response.
        • Similarly, use BuilderUtils methods to create whatever objects are needed.
        Show
        Vinod Kumar Vavilapalli added a comment - Let's have the test do something like this: In the first heartbeat, report no containers and make it succeed In the second heartbeat, reported two running, two completed and one more running containers in that order. But make the hearbeat fail with an exception In heartbeat #3, report the previous completed containers, add one more running and one more finished container. You should control the NM reporting containers by using your custom NMContext and return different container lists on each call to getContainers() . Also, in the test-case, You can use the newly added YarnServerBuilderUtils for constructing node-heartbeat response. Similarly, use BuilderUtils methods to create whatever objects are needed.
        Hide
        Xuan Gong added a comment -

        1.Use YarnServerBuilderUtils for constructing node-heartbeat response
        2.User BuilderUtils to create ApplicationId, ContainerId, ContainerStatus, etc
        3.Recreated the test case as last comment suggested

        Show
        Xuan Gong added a comment - 1.Use YarnServerBuilderUtils for constructing node-heartbeat response 2.User BuilderUtils to create ApplicationId, ContainerId, ContainerStatus, etc 3.Recreated the test case as last comment suggested
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12576650/YARN-101.5.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/649//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/649//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12576650/YARN-101.5.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/649//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/649//console This message is automatically generated.
        Hide
        Xuan Gong added a comment -

        recreate test case to verify status of all containers in every heartbeat

        Show
        Xuan Gong added a comment - recreate test case to verify status of all containers in every heartbeat
        Hide
        Hadoop QA added a comment -

        +1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12576714/YARN-101.6.patch
        against trunk revision .

        +1 @author. The patch does not contain any @author tags.

        +1 tests included. The patch appears to include 1 new or modified test files.

        +1 javac. The applied patch does not increase the total number of javac compiler warnings.

        +1 javadoc. The javadoc tool did not generate any warning messages.

        +1 eclipse:eclipse. The patch built with eclipse:eclipse.

        +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        +1 core tests. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-YARN-Build/658//testReport/
        Console output: https://builds.apache.org/job/PreCommit-YARN-Build/658//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12576714/YARN-101.6.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +1 findbugs . The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit . The applied patch does not increase the total number of release audit warnings. +1 core tests . The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/658//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/658//console This message is automatically generated.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        Looks much better, +1, checking it in.

        Show
        Vinod Kumar Vavilapalli added a comment - Looks much better, +1, checking it in.
        Hide
        Vinod Kumar Vavilapalli added a comment -

        I just committed this to trunk, and branch-2. Thanks Xuan!

        Show
        Vinod Kumar Vavilapalli added a comment - I just committed this to trunk, and branch-2. Thanks Xuan!
        Hide
        Hudson added a comment -

        Integrated in Hadoop-trunk-Commit #3554 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3554/)
        YARN-101. Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105)

        Result = SUCCESS
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105
        Files :

        • /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/NodeManager.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java
        Show
        Hudson added a comment - Integrated in Hadoop-trunk-Commit #3554 (See https://builds.apache.org/job/Hadoop-trunk-Commit/3554/ ) YARN-101 . Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105 Files : /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/NodeManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Yarn-trunk #174 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/174/)
        YARN-101. Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105)

        Result = SUCCESS
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105
        Files :

        • /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/NodeManager.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java
        Show
        Hudson added a comment - Integrated in Hadoop-Yarn-trunk #174 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/174/ ) YARN-101 . Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105 Files : /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/NodeManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Hdfs-trunk #1363 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1363/)
        YARN-101. Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105)

        Result = FAILURE
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105
        Files :

        • /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/NodeManager.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java
        Show
        Hudson added a comment - Integrated in Hadoop-Hdfs-trunk #1363 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1363/ ) YARN-101 . Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105) Result = FAILURE vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105 Files : /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/NodeManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java
        Hide
        Hudson added a comment -

        Integrated in Hadoop-Mapreduce-trunk #1390 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1390/)
        YARN-101. Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105)

        Result = SUCCESS
        vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105
        Files :

        • /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/NodeManager.java
        • /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java
        Show
        Hudson added a comment - Integrated in Hadoop-Mapreduce-trunk #1390 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1390/ ) YARN-101 . Fix NodeManager heartbeat processing to not lose track of completed containers in case of dropped heartbeats. Contributed by Xuan Gong. (Revision 1464105) Result = SUCCESS vinodkv : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1464105 Files : /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/NodeManager.java /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeStatusUpdaterImpl.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/TestNodeStatusUpdater.java

          People

          • Assignee:
            Xuan Gong
            Reporter:
            xieguiming
          • Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development