hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3788) distcp can't copy large files using webhdfs due to missing Content-Length header
Date Wed, 15 Aug 2012 13:30:38 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435093#comment-13435093

Daryn Sharp commented on HDFS-3788:

You're right Nicholas, both headers aren't supposed to be sent and chunked takes prio if they

Pure suggestion, but maybe change the length comparison from {{filelength >= 0}} to {{filelength
!= -1}} or maybe better yet use a boolean.  I don't particularly mind though.

I saw that {{TestByteRangeInputStream#testByteRange}} uses a spied connection object.  I didn't
know if the same technique could be used.  Unfortunately I have zero time to investigate...

+1 It'd be a shame to have no test, but I'll defer to your discretion.
> distcp can't copy large files using webhdfs due to missing Content-Length header
> --------------------------------------------------------------------------------
>                 Key: HDFS-3788
>                 URL: https://issues.apache.org/jira/browse/HDFS-3788
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 0.23.3, 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Tsz Wo (Nicholas), SZE
>            Priority: Critical
>         Attachments: 20120814NullEntity.patch, distcp-webhdfs-errors.txt, h3788_20120813.patch,
h3788_20120814b.patch, h3788_20120814.patch
> The following command fails when data1 contains a 3gb file. It passes when using hftp
or when the directory just contains smaller (<2gb) files, so looks like a webhdfs issue
with large files.
> {{hadoop distcp webhdfs://eli-thinkpad:50070/user/eli/data1 hdfs://localhost:8020/user/eli/data2}}

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


View raw message