[
https://issues.apache.org/jira/browse/HADOOP-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590590#action_12590590
]
Devaraj Das commented on HADOOP-1650:
-------------------------------------
Michael, the last time we benchmarked, the results were not satisfactory.
Changing the jetty version is a big deal and we need to be absolutely sure
about performance/reliability degradations since the current version in hadoop
is pretty good in terms of reliability and reasonably ok in terms of
performance...
So please bear with us while we test/benchmark to make sure that jetty6 is at
least as good as jetty5... This might take some time since it involves testing
on large clusters and that requires some co-ordination with other folks ...
> 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-20080120.patch, 1650-jetty6.1.9.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.
