Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-3896

RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset synchronously

    Details

    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      2015-07-03 16:49:39,075 INFO org.apache.hadoop.yarn.util.RackResolver: Resolved 10.208.132.153 to /default-rack
      2015-07-03 16:49:39,075 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: Reconnect from the node at: 10.208.132.153
      2015-07-03 16:49:39,075 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: NodeManager from node 10.208.132.153(cmPort: 8041 httpPort: 8080) registered with capability: <memory:6144, vCores:60, diskCapacity:213>, assigned nodeId 10.208.132.153:8041
      2015-07-03 16:49:39,104 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: Too far behind rm response id:2506413 nm response id:0
      2015-07-03 16:49:39,137 INFO org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: Deactivating Node 10.208.132.153:8041 as it is now REBOOTED
      2015-07-03 16:49:39,137 INFO org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: 10.208.132.153:8041 Node Transitioned from RUNNING to REBOOTED
      

      The node(10.208.132.153) reconnected with RM. When it registered with RM, RM set its lastNodeHeartbeatResponse's id to 0 asynchronously. But the node's heartbeat come before RM succeeded setting the id to 0.

        Attachments

        1. YARN-3896.07.patch
          9 kB
          Jun Gong
        2. 0001-YARN-3896.patch
          9 kB
          Rohith Sharma K S
        3. YARN-3896.06.patch
          9 kB
          Jun Gong
        4. YARN-3896.05.patch
          10 kB
          Jun Gong
        5. YARN-3896.04.patch
          10 kB
          Jun Gong
        6. YARN-3896.03.patch
          10 kB
          Jun Gong
        7. YARN-3896.02.patch
          6 kB
          Jun Gong
        8. YARN-3896.01.patch
          3 kB
          Jun Gong

          Activity

            People

            • Assignee:
              hex108 Jun Gong
              Reporter:
              hex108 Jun Gong
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: