[
https://issues.apache.org/jira/browse/YARN-7102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310045#comment-16310045
]
Botong Huang commented on YARN-7102:
------------------------------------
Hi [~jlowe], in v15 patch I moved part of the reconnect logic into
ResourceTrackerService.registerNodeManager as you suggested. The specific
condition where we replace with a new RMNode is a bit weird though. Reading the
original code in ReconnectNodeTransition, various conditions about when to swap
the node and when to call NodeResourceUpdateSchedulerEvent seems inconsistent.
I am wondering if it is possible to always not swap and use the existing
RMNode. Please let me know what you think, thanks!
> NM heartbeat stuck when responseId overflows MAX_INT
> ----------------------------------------------------
>
> Key: YARN-7102
> URL: https://issues.apache.org/jira/browse/YARN-7102
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Botong Huang
> Assignee: Botong Huang
> Priority: Critical
> Attachments: YARN-7102-branch-2.8.v10.patch,
> YARN-7102-branch-2.8.v11.patch, YARN-7102-branch-2.8.v14.patch,
> YARN-7102-branch-2.8.v14.patch, YARN-7102-branch-2.8.v9.patch,
> YARN-7102-branch-2.v14.patch, YARN-7102-branch-2.v14.patch,
> YARN-7102-branch-2.v9.patch, YARN-7102-branch-2.v9.patch,
> YARN-7102-branch-2.v9.patch, YARN-7102.v1.patch, YARN-7102.v12.patch,
> YARN-7102.v13.patch, YARN-7102.v14.patch, YARN-7102.v15.patch,
> YARN-7102.v2.patch, YARN-7102.v3.patch, YARN-7102.v4.patch,
> YARN-7102.v5.patch, YARN-7102.v6.patch, YARN-7102.v7.patch,
> YARN-7102.v8.patch, YARN-7102.v9.patch
>
>
> ResponseId overflow problem in NM-RM heartbeat. This is same as AM-RM
> heartbeat in YARN-6640, please refer to YARN-6640 for details.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
