[
https://issues.apache.org/jira/browse/YARN-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803568#comment-13803568
]
Alejandro Abdelnur commented on YARN-1343:
------------------------------------------
bq. 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.
IMO this suggestion is a separate JIRA and it will required changes in the API.
What this JIRA is fixing a bug where a AM never gets notified via updates with
a node is RUNNING (for the first time or again), only when a node goes !RUNNING.
> 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)
