[
https://issues.apache.org/jira/browse/HADOOP-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414276#comment-13414276
]
Zhihong Ted Yu commented on HADOOP-8350:
----------------------------------------
I was running HBase test suite against hadoop 2.0 and observed the following
test failure:
{code}
testCalls(org.apache.hadoop.hbase.ipc.TestPBOnWritableRpc) Time elapsed: 0.002
sec <<< ERROR!
java.io.IOException: java.lang.NoSuchMethodError:
org.apache.hadoop.net.NetUtils.getInputStream(Ljava/net/Socket;)Ljava/io/InputStream;
...
Caused by: java.lang.NoSuchMethodError:
org.apache.hadoop.net.NetUtils.getInputStream(Ljava/net/Socket;)Ljava/io/InputStream;
at
org.apache.hadoop.hbase.ipc.HBaseClient$Connection.setupIOstreams(HBaseClient.java:693)
at
org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1305)
at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1157)
at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Invoker.invoke(WritableRpcEngine.java:152)
at $Proxy37.getProtocolVersion(Unknown Source)
{code}
Here was the command I used:
{code}
mvn help:active-profiles -Dhadoop.profile=2.0 test
{code}
I believe the above exception was caused by this JIRA.
> Improve NetUtils.getInputStream to return a stream which has a tunable timeout
> ------------------------------------------------------------------------------
>
> Key: HADOOP-8350
> URL: https://issues.apache.org/jira/browse/HADOOP-8350
> Project: Hadoop Common
> Issue Type: Improvement
> Components: util
> Affects Versions: 1.0.0, 2.0.0-alpha
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Fix For: 2.0.0-alpha
>
> Attachments: hadoop-8350.txt, hadoop-8350.txt, hadoop-8350.txt
>
>
> Currently, NetUtils.getInputStream will set the timeout on the new stream
> based on the socket's configured timeout at the time of construction. After
> that, the timeout cannot be changed. This causes a problem for cases like
> HDFS-3357. One approach used in some places in the code is to construct new
> streams when the timeout has to be changed, but this can cause bugs given
> that the streams are often wrapped by BufferedInputStreams.
--
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
