Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A232D10C10 for ; Thu, 20 Feb 2014 01:17:26 +0000 (UTC) Received: (qmail 81864 invoked by uid 500); 20 Feb 2014 01:17:25 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 81723 invoked by uid 500); 20 Feb 2014 01:17:24 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 81681 invoked by uid 99); 20 Feb 2014 01:17:24 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Feb 2014 01:17:24 +0000 Date: Thu, 20 Feb 2014 01:17:24 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)