[
https://issues.apache.org/jira/browse/HADOOP-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644828#action_12644828
]
Greg Wilkins commented on HADOOP-1650:
--------------------------------------
I'm currently working on a Jetty extension that will better suit the Hadoop use
case, namely serving ranges of very large files. The extension will wrap a
RandomAccessFile instance as a Jetty buffer and thus will be able to be passed
to in Http Generator within Jetty and
asynchronously flushed using FileChannel.transferTo(Channel)
This is mostly written now and we will be benchmarking this shortly.
Unfortunately, this will not make it into the Jetty 6.1.12 final release (out
later today), but that does have some optimizations over 6.1.12.rc4
> Upgrade Jetty to 6.x
> --------------------
>
> Key: HADOOP-1650
> URL: https://issues.apache.org/jira/browse/HADOOP-1650
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Attachments: 1650-0.patch, 1650-20080120.patch,
> 1650-jetty6.1.9.patch, 1650-jetty6.1.9.v1.patch,
> hadoop-1650-jetty6.1.5.patch, hadoop-jetty6.1.4-lib.tar.gz,
> hadoop-jetty6.1.6-lib.tar.gz, hadoop-jetty6.1.9-lib.tar.gz,
> jetty-hadoop-6.1.6.patch, jetty-hbase.patch, jetty6.1.4.patch,
> jetty6.1.6.patch
>
>
> This is the third attempt at moving to jetty6. Apparently, the jetty-6.1.4
> has fixed some of the issues we discovered in jetty during HADOOP-736 and
> HADOOP-1273. I'd like to keep this issue open for sometime so that we have
> enough time to test out things.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
