[
https://issues.apache.org/jira/browse/HADOOP-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267829#comment-13267829
]
Hadoop QA commented on HADOOP-8350:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12525510/hadoop-8350.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified test
files.
-1 javadoc. The javadoc tool appears to have generated 2 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.fs.viewfs.TestViewFsTrash
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/932//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/932//console
This message is automatically generated.
> 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
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: 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
