[
https://issues.apache.org/jira/browse/YARN-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528057#comment-16528057
]
Hudson commented on YARN-8451:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14503 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14503/])
YARN-8451. Multiple NM heartbeat thread created when a slow NM resync (jlowe:
rev 100470140d86eede0fa240a9aa93226f274ee4f5)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/NodeManager.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/test/java/org/apache/hadoop/yarn/server/nodemanager/TestNodeManagerResync.java
> Multiple NM heartbeat thread created when a slow NM resync with RM
> ------------------------------------------------------------------
>
> Key: YARN-8451
> URL: https://issues.apache.org/jira/browse/YARN-8451
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Major
> Fix For: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 3.0.4
>
> Attachments: YARN-8451.v1.patch, YARN-8451.v2.patch
>
>
> During a NM resync with RM (say RM did a master slave switch), if NM is
> running slow, more than one RESYNC event may be put into the NM dispatcher by
> the existing heartbeat thread before they are processed. As a result,
> multiple new heartbeat thread are later created and start to hb to RM
> concurrently with their own responseId. If at some point of time, one thread
> becomes more than one step behind others, RM will send back a resync signal
> in this heartbeat response, killing all containers in this NM.
> See comments below for details on how this can happen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
