[ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906425#comment-13906425 ]
Vinod Kumar Vavilapalli commented on YARN-713: ---------------------------------------------- Yes, I did see the issue on branch-2.4 during review itself and fixed it manually. Forgot during commit. Fixing it rightaway. > 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: Jian He > Priority: Critical > Fix For: 2.4.0 > > Attachments: YARN-713.09052013.1.patch, YARN-713.09062013.1.patch, > YARN-713.1.patch, YARN-713.2.patch, YARN-713.20130910.1.patch, > YARN-713.3.patch, YARN-713.4.patch, YARN-713.5.patch, YARN-713.6.patch, > 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 was sent by Atlassian JIRA (v6.1.5#6160)