[
https://issues.apache.org/jira/browse/YARN-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344739#comment-14344739
]
Rohith commented on YARN-3222:
------------------------------
Had a mail chat with [~jianhe] regarding the issue's observed in this jira
discussions and decided to split up the jira into 2 separate jira. The observed
issues in ReconnectNodeTransition are
# As per defect description, order of node_resource_update and node_added
events sending to schedulers. If Node_added events is being sent to schedulers
then no need of sending node_resource_update event from RMNode again to
scheduler which is not necessarily required.
# If the RMNode state is RUNNING then Node_usable event not necessarily to be
sent.
# If a node is reconnceted with different capability, then
RMNode#totalCapability remains with old capability. This has to be updated with
new capability.
1 and 2 are going to handle in this jira. 3 issue will be done in separate jira.
> RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential
> order
> -----------------------------------------------------------------------------------
>
> Key: YARN-3222
> URL: https://issues.apache.org/jira/browse/YARN-3222
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.6.0
> Reporter: Rohith
> Assignee: Rohith
> Priority: Critical
> Attachments: 0001-YARN-3222.patch, 0002-YARN-3222.patch,
> 0003-YARN-3222.patch
>
>
> When a node is reconnected,RMNodeImpl#ReconnectNodeTransition notifies the
> scheduler in a events node_added,node_removed or node_resource_update. These
> events should be notified in an sequential order i.e node_added event and
> next node_resource_update events.
> But if the node is reconnected with different http port, the oder of
> scheduler events are node_removed --> node_resource_update --> node_added
> which causes scheduler does not find the node and throw NPE and RM exit.
> Node_Resource_update event should be always should be triggered via
> RMNodeEventType.RESOURCE_UPDATE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
