[ 
https://issues.apache.org/jira/browse/YARN-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jun Gong updated YARN-3896:
---------------------------
    Description: 
{noformat}
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
{noformat}

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.

  was:
{noformat}
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
{noformat}


> RMNode transitioned from RUNNING to REBOOTED because its response id had not 
> been reset
> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-3896
>                 URL: https://issues.apache.org/jira/browse/YARN-3896
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>            Reporter: Jun Gong
>            Assignee: Jun Gong
>
> {noformat}
> 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
> {noformat}
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to