Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 14 Jun 2013 08:57:21 +0000 (UTC)
From: "Maysam Yabandeh (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12648761.1369176650395.114429.1371200241921@arcas>
In-Reply-To: <JIRA.12648761.1369176650395@arcas>
References: <JIRA.12648761.1369176650395@arcas>
Subject: [jira] [Updated] (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


     [ https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maysam Yabandeh updated YARN-713:
---------------------------------

    Attachment: YARN-713.patch

The attached patch is updated with latest trunk changes.
                
> 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: Maysam Yabandeh
>            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