[jira] [Updated] (MAPREDUCE-4295) RM crashes due to DNS issue

["Thomas Graves (JIRA)" <ji...@apache.org>]

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

Thomas Graves updated MAPREDUCE-4295:
-------------------------------------

    Attachment: MAPREDUCE-4295.patch

This patch fixes the crash.  Now it simply catches the exception and returns that no resources were allocated and continues.  

I tested this manually on a small cluster and verified that works.  I verified when DNS comes back up on the RM starts working and allocating containers again.
                
> RM crashes due to DNS issue
> ---------------------------
>
>                 Key: MAPREDUCE-4295
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4295
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, resourcemanager
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>            Priority: Critical
>             Fix For: 0.23.3
>
>         Attachments: MAPREDUCE-4295.patch
>
>
> we had a DNS outage and the RM crashed with the following backtrace:
> 2012-05-29 19:17:34,492 FATAL
> org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error in
> handling event type NODE_UPDATE to the scheduler
> java.lang.IllegalArgumentException: java.net.UnknownHostException:
> host.com        at
> org.apache.hadoop.security.SecurityUtil.buildTokenService(SecurityUtil.java:430)
>         at
> org.apache.hadoop.yarn.util.BuilderUtils.newContainerToken(BuilderUtils.java:261)
>        at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.createContainer(LeafQueue.java:1184)
>         at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.getContainer(LeafQueue.java:1167)
>         at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue.assignContainer(LeafQueue.java:1213)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira