[
https://issues.apache.org/jira/browse/HADOOP-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799818#action_12799818
]
Steve Loughran commented on HADOOP-6220:
----------------------------------------
Seen in trying to shut down nodes as they come up; it's nice to be able to
differentiate "we interrupted you" from "something went wrong".
Changing the signature? It's more dramatic, but yes, more explicit.
> 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
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: 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 IOE
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
