[
https://issues.apache.org/jira/browse/HDFS-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422036#comment-13422036
]
Hadoop QA commented on HDFS-3696:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12537802/h3696_20120724.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 1 new or modified test
files.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+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-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestReplication
org.apache.hadoop.hdfs.TestDatanodeBlockScanner
org.apache.hadoop.hdfs.TestPersistBlocks
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2901//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2901//console
This message is automatically generated.
> FsShell put using WebHdfsFileSystem goes OOM when file size is big
> ------------------------------------------------------------------
>
> Key: HDFS-3696
> URL: https://issues.apache.org/jira/browse/HDFS-3696
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.0.0-alpha
> Reporter: Kihwal Lee
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Critical
> Fix For: 0.23.3, 3.0.0, 2.2.0-alpha
>
> Attachments: h3696_20120724.patch
>
>
> When doing "fs -put" to a WebHdfsFileSystem (webhdfs://), the FsShell goes
> OOM if the file size is large. When I tested, 20MB files were fine, but 200MB
> didn't work.
> I also tried reading a large file by issuing "-cat" and piping to a slow sink
> in order to force buffering. The read path didn't have this problem. The
> memory consumption stayed the same regardless of progress.
--
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
