[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727210#comment-13727210 ]
Omkar Vinit Joshi commented on YARN-713: ---------------------------------------- [~daryn] [~vinodkv] any reason why we are not throwing UnknownHostException directly instead of wrapping it inside IllegalArgumentException? By doing this we are actually hiding static exception like this into a RuntimeException. Probably we should expose UnknownHostException thereby all the users will be forced to handle it. {code} public static Text buildTokenService(InetSocketAddress addr) { String host = null; if (useIpForTokenService) { if (addr.isUnresolved()) { // host has no ip address throw new IllegalArgumentException( new UnknownHostException(addr.getHostName()) ); } host = addr.getAddress().getHostAddress(); } else { host = addr.getHostName().toLowerCase(); } return new Text(host + ":" + addr.getPort()); } {code} > 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