[
https://issues.apache.org/jira/browse/YARN-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803514#comment-13803514
]
Bikas Saha commented on YARN-1343:
----------------------------------
Should we create a NODE_ADDED instead of overloading NODE_USABLE in case
downstream consumers need to differentiate the cases. The update type enum (eg.
NODE_USABLE) is passed in the event sent to the consumers (in this case RMApp).
Reconnect of a NM after restart has 2 cases, it comes back with identical
state/resources. Does the app need to know about this? It comes back with
different state. Does the app need to know about this? If the answer is yes to
both then do the 2 situations need to be differentiated?
> 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
>
> Attachments: YARN-1343.patch
>
>
> 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)
