hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Wilkins (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1650) Upgrade Jetty to 6.x
Date Wed, 15 Oct 2008 04:06:44 GMT

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

Greg Wilkins commented on HADOOP-1650:
--------------------------------------

Note that in an email conversation many months ago with somebody, I realized that one of your
problems with performance was almost certainly that the default threadpool size had been reduced
from 255 to 50 threads in jetty.  This was because we are mostly using the NIO connector.
But if hadoop is still using the socket connector, then it will need a larger threadpool



> 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, 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.


Mime
View raw message