[ 
https://issues.apache.org/jira/browse/HDFS-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kihwal Lee updated HDFS-3696:
-----------------------------

    Description: 
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.


  was:
When dong "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.


    
> 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
>            Priority: Critical
>             Fix For: 0.23.3, 3.0.0, 2.2.0-alpha
>
>
> 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

        

Reply via email to