[
https://issues.apache.org/jira/browse/HADOOP-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646778#action_12646778
]
Chris Douglas commented on HADOOP-1650:
---------------------------------------
Merged patch with trunk.
The HdfsProxy code was recently checked into contrib. The \_merge and \_delta
patches subclass ProxyHttpServer from HttpServer to collapse some common
functionality (i.e. upgrading the former to use Jetty6, though this doesn't
update the packaging). This may not be the appropriate solution for that
component; it may require Jetty5. I'll leave that up to someone with more
insight into its particular use cases. Some of the changes to HttpServer from
these patches would do well merged back into the original, but that can wait
until contrib is sorted out. If we move to Jetty6, Chukwa should also use the
jars out of lib instead of keeping its own copies.
If mapred performance doesn't degrade using the basic upgrade- or if it only
degrades slightly- we can move the TaskTracker optimization to a separate
issue. We should also run gridmix to make sure we don't have any stability
problems.
> 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-1_core.patch, 1650-1_merge.patch,
> 1650-1_proxy_delta.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.
