hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1650) Upgrade Jetty to 6.x
Date Sun, 30 Nov 2008 01:04:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651770#action_12651770
] 

Chris Douglas commented on HADOOP-1650:
---------------------------------------

{quote}
In your patch(converting jetty5 to 6), I noticed that SelectChannelConnector.setUseDirectBuffers(boolean)
is set to false.
Any reason behind it?
{quote}
Deveraj ran into some GC issues in the last attempted migration (above) and some previous
experiences with direct buffers left me wary. For the initial checkin, it made more sense
to track down any stability problems we run into without the direct buffer noise. We can certainly
revisit it when considering other optimizations and I certainly wouldn't be against making
it configurable.

> 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: Chris Douglas
>             Fix For: 0.20.0
>
>         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, shuffleData.zip
>
>
> 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.


Mime
View raw message