[
https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727692#comment-13727692
]
Daryn Sharp commented on YARN-713:
----------------------------------
I wanted to change that long ago, but the problem is the ripple effect of
adding a checked exception to the signature.
I actually started to change this code at one time because there's no reason
that the address should be resolved for every token. I split the patch out of
a larger change (and then lost it) but I made the nodeId store the
{{InetSocketAddress}}. I added {{getSocketAddr}} so it could be queried for
{{setTokenService}} and other places that needlessly keep reconstructing an
{{InetSocketAddress}}.
> ResourceManager can exit unexpectedly if DNS is unavailable
> -----------------------------------------------------------
>
> Key: YARN-713
> URL: https://issues.apache.org/jira/browse/YARN-713
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.1.0-beta
> Reporter: Jason Lowe
> Assignee: Omkar Vinit Joshi
> Priority: Critical
> Fix For: 2.1.0-beta
>
> Attachments: YARN-713.patch, YARN-713.patch, YARN-713.patch,
> YARN-713.patch
>
>
> As discussed in MAPREDUCE-5261, there's a possibility that a DNS outage could
> lead to an unhandled exception in the ResourceManager's AsyncDispatcher, and
> that ultimately would cause the RM to exit. The RM should not exit during
> DNS hiccups.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
