hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kihwal Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4387) RM gets fatal error and exits during TestRM
Date Fri, 29 Jun 2012 21:03:44 GMT

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

Kihwal Lee commented on MAPREDUCE-4387:
---------------------------------------

{{EventProcessor#stop()}} is setting {stopped} to true before interrupting the thread. So
we could just add one more condition and let it terminate normally.

{code}
        while (!stopped && !Thread.currentThread().isInterrupted()) {
          try {
            event = eventQueue.take();
          } catch (InterruptedException e) {
            LOG.error("Returning, interrupted : " + e);
            return; // TODO: Kill RM.
          }

          try {
            scheduler.handle(event);
          } catch (Throwable t) {
+           if (stopped) {
+             LOG.warn("Exception during shutdown: ", t);
+             break;
+           }
            LOG.fatal("Error in handling event type " + event.getType()
                + " to the scheduler", t);
            if (shouldExitOnError
                && !ShutdownHookManager.get().isShutdownInProgress()) {
              LOG.info("Exiting, bbye..");
              System.exit(-1);
            }
          }
        }
{code}
                
> RM gets fatal error and exits during TestRM
> -------------------------------------------
>
>                 Key: MAPREDUCE-4387
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4387
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.0.0-alpha
>            Reporter: Kihwal Lee
>             Fix For: 2.0.1-alpha, 3.0.0
>
>
> It doesn't happen on my desktop, but it happens frequently during the builds with clover
enabled. Surefire will report it as fork failure.

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

        

Mime
View raw message