[ https://issues.apache.org/jira/browse/HADOOP-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13116803#comment-13116803
]
Hudson commented on HADOOP-6220:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #982 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/982/])
HADOOP-6220
stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1177051
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/http/HttpServer.java
> 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.20.204.0, 0.21.0, 0.22.0, 0.23.0, 0.24.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Fix For: 0.24.0
>
> Attachments: HADOOP-6220-trunk.patch, 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
IOE
--
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
|