[
https://issues.apache.org/jira/browse/YARN-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029143#comment-14029143
]
Jason Lowe commented on YARN-1885:
----------------------------------
bq. Is this an existing bug? reconnected event is sent to the NEW node instead
of the old node. we can fix this separately, if this is.
I don't think that's a bug. Note that NodeEventDispatcher will dispatch the
reconnected event to the RMNode that is registered in the RMContext with
nodeId, and putIfAbsent will preserve the old node in that mapping. It passes
the new node in the event payload so the old node can examine the
re-registration details during reconnect processing.
> RM may not send the finished signal to some nodes where the application ran
> after RM restarts
> ---------------------------------------------------------------------------------------------
>
> Key: YARN-1885
> URL: https://issues.apache.org/jira/browse/YARN-1885
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Arpit Gupta
> Assignee: Wangda Tan
> Attachments: YARN-1885.patch, YARN-1885.patch, YARN-1885.patch,
> YARN-1885.patch, YARN-1885.patch, YARN-1885.patch, YARN-1885.patch
>
>
> During our HA testing we have seen cases where yarn application logs are not
> available through the cli but i can look at AM logs through the UI. RM was
> also being restarted in the background as the application was running.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
