[jira] [Commented] (YARN-3222) RMNodeImpl#ReconnectNodeTransition should send scheduler events in sequential order

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on YARN-3222:
------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #8382 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/8382/])
YARN-3222. Added the missing CHANGES.txt entry. (vinodkv: rev 4620767156ecc43424bc6c7c4d50519e2563cc69)
* hadoop-yarn-project/CHANGES.txt


> 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 Sharma K S
>            Assignee: Rohith Sharma K S
>            Priority: Critical
>              Labels: 2.6.1-candidate
>             Fix For: 2.7.0, 2.6.1
>
>         Attachments: 0001-YARN-3222.patch, 0002-YARN-3222.patch, 0003-YARN-3222.patch, 0004-YARN-3222.patch, 0005-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)