[
https://issues.apache.org/jira/browse/YARN-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803648#comment-13803648
]
Bikas Saha commented on YARN-1343:
----------------------------------
This is not a bug since sending the AM information about added/removed nodes is
a feature that was never added to the RM. The feature was added to reporting
healthy/unhealthy updates for an existing node. So adding support to notify
about additions/removals is an improvement and I like this improvement. I am
trying to understand how we can make this improvement useful to the AM that
receive this information.
If we simply send the nodestatus object to the AM how is the AM expected to
make sense of it? Are there any existing fields in nodestatus that tell the AM
about addition/reconnection? If not, then is this patch complete wrt the intent
of the jira to inform AMs about addition/reconnection and (potentially removal)?
> 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)
