[
https://issues.apache.org/jira/browse/YARN-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803565#comment-13803565
]
Bikas Saha commented on YARN-1343:
----------------------------------
Also, to be clear, the original code was added to update the AM about
unhealthy/healthy node changes in order to reach compatibility with MR1. Here
we are making an addition to that mechanism to also pass the added/reconnected
nodes. That is a useful improvement. We can also pass removed node information
to complete all the cases. My suggestion is to pass the additional information
in the NodeStatus object that is sent to the AM. The additional status would be
what the change was. addition, unhealthy, healthy, restarted/reconnected,
removed.
> 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)
