hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3896) RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset synchronously
Date Mon, 24 Aug 2015 08:21:47 GMT

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

Hudson commented on YARN-3896:
------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk-Java8 #299 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Java8/299/])
YARN-3896. RMNode transitioned from RUNNING to REBOOTED because its response id has not been
reset synchronously. (Jun Gong via rohithsharmaks) (rohithsharmaks: rev feaf0349949e831ce3f25814c1bbff52f17bfe8f)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ResourceTrackerService.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNodeImpl.java
* hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/scheduler/RMNodeWrapper.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/rmnode/RMNode.java
* hadoop-yarn-project/CHANGES.txt
* hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/nodemanager/NodeInfo.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/resourcetracker/TestNMReconnect.java


> RMNode transitioned from RUNNING to REBOOTED because its response id had not been reset
synchronously
> -----------------------------------------------------------------------------------------------------
>
>                 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
>              Labels: resourcemanager
>             Fix For: 2.8.0
>
>         Attachments: 0001-YARN-3896.patch, YARN-3896.01.patch, YARN-3896.02.patch, YARN-3896.03.patch,
YARN-3896.04.patch, YARN-3896.05.patch, YARN-3896.06.patch, YARN-3896.07.patch
>
>
> {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)

Mime
View raw message