hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6220) HttpServer wraps InterruptedExceptions by IOExceptions if interrupted in startup
Date Mon, 21 Feb 2011 13:27:38 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997396#comment-12997396

Steve Loughran commented on HADOOP-6220:

No tests as it's so hard to recreate this situation in a test; you need one thread sleeping
and another interrupting. 

> HttpServer wraps InterruptedExceptions by IOExceptions if interrupted in startup
> --------------------------------------------------------------------------------
>                 Key: HADOOP-6220
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6220
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 0.21.0, 0.22.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-6220.patch, HADOOP-6220.patch
> Following on some discusson on mapred-dev, we should keep an eye on the fact that Jetty
uses sleeps when starting up; jetty can be a big part of the delays of bringing up a node.
When interrupted, the exception is wrapped by an IOException, the root cause is still there,
just hidden.
> If we want callers to distinguish InterruptedExceptions from IOEs, then this exception
should be extracted. Some helper method to start an http daemon could do this -catch the IOE,
and if there is a nested interrupted exception, rethrow it, otherwise rethrowing the original

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message