[
https://issues.apache.org/jira/browse/HDFS-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190671#comment-14190671
]
Hadoop QA commented on HDFS-7224:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12678284/HDFS-7224.v1.201410301923.txt
against trunk revision c2866ac.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8600//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
>
>
> 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)
