[ 
https://issues.apache.org/jira/browse/YARN-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906304#comment-13906304
 ] 

Arpit Agarwal commented on YARN-713:
------------------------------------

Is this error in branch-2.4 related?

{code}
WARN: Please see http://www.slf4j.org/codes.html for an explanation.
[ERROR] COMPILATION ERROR :
[ERROR] 
/Users/aagarwal/src/commit/branch-2.4/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/Allocation.java:[32,16]
 cannot find symbol
symbol  : class RecordFactory
location: class 
org.apache.hadoop.yarn.server.resourcemanager.scheduler.Allocation
[ERROR] 
/Users/aagarwal/src/commit/branch-2.4/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/Allocation.java:[33,6]
 cannot find symbol
{code}

Thanks.

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

Reply via email to