[
https://issues.apache.org/jira/browse/HDFS-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281007#comment-14281007
]
Hadoop QA commented on HDFS-7224:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12692828/HDFS-7224.v4.txt
against trunk revision ec4389c.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9254//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9254//console
This message is automatically generated.
> Allow reuse of NN connections via webhdfs
> -----------------------------------------
>
> Key: HDFS-7224
> URL: https://issues.apache.org/jira/browse/HDFS-7224
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 2.5.0
> Reporter: Eric Payne
> Assignee: Eric Payne
> Attachments: HDFS-7224.v1.201410301923.txt,
> HDFS-7224.v2.201410312033.txt, HDFS-7224.v3.txt, HDFS-7224.v4.txt
>
>
> In very large clusters, the webhdfs client could get bind exceptions because
> it runs out of ephemeral
> ports. This could happen when using webhdfs to talk to the NN in order to do
> list globbing of a
> huge amount of files.
> WebHdfsFileSystem#jsonParse gets the input/error stream from the connection,
> but never closes the stream. Since it's not closed, the JVM thinks the stream
> may still
> be transferring data, so the next time through this code, it has to get a new
> connection
> rather than reusing an existing one.
> The lack of connection reuse has poor latency and adds too much overhead to
> the NN.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
