[
https://issues.apache.org/jira/browse/HADOOP-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-1650:
----------------------------------
Attachment: 1650-2.patch
Updated patch. I tested this using gridmix2 (HADOOP-3770) and found the
performance to be comparable to trunk with the same configuration (387 nodes,
39m0s; trunk is about 36m with 400 nodes) using Jetty 6.1.14. It passes all
unit tests, but generated findbugs warnings for non-serializable/transient
fields
([SE_BAD_FIELD|http://findbugs.sourceforge.net/bugDescriptions.html#SE_BAD_FIELD])
in the jsps. I made an attempt to update the eclipse classpath; if someone
could verify that this works for them, that would be helpful.
> 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-2.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.
