hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4549) WebHDFS hits a Jetty performance issue
Date Thu, 18 Apr 2013 20:14:13 GMT

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

Alejandro Abdelnur commented on HDFS-4549:

I think we should leave Jersey to decide what to use, chunk encoding or not. If we always
force the content-length, we can run into issues in clients (I believe Java HTTP does -or
used to do this-) that try to allocate a buffer in memory for the full content-length. By
using chunk encoding, you are forcing the client to fallback on partial-caching/flushing.

Is the Jetty version use by Hadoop 1 that has issues with chunk encoding?

Also, if we don't see the problem in trunk/branch-2, why change it there? not broken, don't
fix it. 

> WebHDFS hits a Jetty performance issue
> --------------------------------------
>                 Key: HDFS-4549
>                 URL: https://issues.apache.org/jira/browse/HDFS-4549
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 1.1.2
>            Reporter: Mark Wagner
>            Assignee: Mark Wagner
>         Attachments: example4549.txt, HDFS-4549.1.patch, HDFS-4549.2.patch
> WebHDFS on branch-1 is hitting a Jetty issue for me when it does chunked transfers. This
is the same Jetty issue as MAPREDUCE-4399. I have not observed this on trunk.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message