[
https://issues.apache.org/jira/browse/YARN-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809753#comment-13809753
]
Bikas Saha commented on YARN-1343:
----------------------------------
Can you please double check that testReconnectWithDifferentCapacity is actually
resulting in reconnection? The test alters the existing node's capacity and
thus I would expect the equality check in ReconnectTransition to consider the
nodes same as before. We probably need to create a new node with same name and
different capacity. Maybe stepping through in the debugger may show whats
really happening.
If reconnect with different capability code is getting executed then I would
expect mock rm context to have to mock getRMNodes() method and a listener to be
added for RMNodeEvents. Or else the test will have exceptions in the output.
> 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, YARN-1343.patch, 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)
