You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2007/07/25 07:15:31 UTC

[jira] Commented: (HADOOP-1650) Upgrade Jetty to 6.x

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

Devaraj Das commented on HADOOP-1650:
-------------------------------------

By the way, in the patch, the default connector is set to SelectChannelConnector. One could also use the SocketConnector or the BlockingChannelConnector by setting up the hadoop config item jetty.connector appropriately (the value should be one of org.mortbay.jetty.bio.SocketConnector, org.mortbay.jetty.nio.BlockingChannelConnector, org.mortbay.jetty.nio.SelectChannelConnector). http://docs.codehaus.org/display/JETTY/Architecture has some insights into each of the connectors. Also, the patch switches Direct ByteBuffers off (due to the associated GC issues).

> Upgrade Jetty to 6.x
> --------------------
>
>                 Key: HADOOP-1650
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1650
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Devaraj Das
>            Assignee: Devaraj Das
>         Attachments: hadoop-jetty6.1.4-lib.tar.gz, jetty6.1.4.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-565 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.