You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-dev@hadoop.apache.org by "Rohith (JIRA)" <ji...@apache.org> on 2015/02/19 05:03:11 UTC

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

Rohith created YARN-3222:
----------------------------

             Summary: 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


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)