You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2014/01/30 21:12:14 UTC

[jira] [Updated] (YARN-713) ResourceManager can exit unexpectedly if DNS is unavailable

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

Jason Lowe updated YARN-713:
----------------------------

    Target Version/s: 2.3.0

> 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
>         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.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)