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 "Maysam Yabandeh (JIRA)" <ji...@apache.org> on 2013/05/31 18:50:20 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13671637#comment-13671637 ] 

Maysam Yabandeh commented on YARN-713:
--------------------------------------

I was preparing a patch for this, but I noticed that after the revert of the patch of MAPREDUCE-5261, the problem reported in MAPREDUCE-5261 still exists, i.e., TestRMContainerAllocator#testSimple throws the exception. I guess I am missing something since [~vinodkv] had reported that this problem is fixed by a change in core-site.xml.
                
> 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.0.5-beta
>            Reporter: Jason Lowe
>            Priority: Critical
>
> 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