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-3671) ByteRangeInputStream shouldn't require the content length header be present
Date Mon, 16 Jul 2012 19:00:43 GMT

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

Daryn Sharp commented on HDFS-3671:
-----------------------------------

Jetty has I think a 200s timeout, so increasing the client read timeout above that should
be a quasi-reasonable workaround.  Unfortunately the client read timeout isn't configurable,
although it should be simple to make it configurable.

You may want to consider investigating how hard it would be to use the size from a file stat
in lieu of a missing content-length.
                
> ByteRangeInputStream shouldn't require the content length header be present
> ---------------------------------------------------------------------------
>
>                 Key: HDFS-3671
>                 URL: https://issues.apache.org/jira/browse/HDFS-3671
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Priority: Blocker
>
> Per HDFS-3318 the content length header check breaks distcp compatibility with previous
releases (0.20.2 and earlier, and 0.21). Like branch-1 this check should be lenient.

--
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

        

Mime
View raw message