hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1343) NodeManagers additions/restarts are not reported as node updates in AllocateResponse responses to AMs
Date Wed, 23 Oct 2013 21:12:41 GMT

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

Alejandro Abdelnur commented on YARN-1343:
------------------------------------------

The problem is that the RMNodeImpl.AddNodeTransition() is not dispatching a NodesListManagerEventType.NODE_USABLE
event to the NodeListManager. Plus, the NodeListManager handle() for NODE_UNUSABLE should
dispatch RMAppNodeUpdateType.NODE_USABLE events to the apps even if the node was not in the
unusable list.


> NodeManagers additions/restarts are not reported as node updates in AllocateResponse
responses to AMs
> -----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1343
>                 URL: https://issues.apache.org/jira/browse/YARN-1343
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.2.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>            Priority: Critical
>             Fix For: 2.2.1
>
>
> If a NodeManager joins the cluster or gets restarted, running AMs never receive the node
update indicating the Node is running.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message