Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 1882 invoked from network); 15 Oct 2008 04:07:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Oct 2008 04:07:07 -0000 Received: (qmail 36260 invoked by uid 500); 15 Oct 2008 04:07:06 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 36222 invoked by uid 500); 15 Oct 2008 04:07:05 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 36210 invoked by uid 99); 15 Oct 2008 04:07:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Oct 2008 21:07:05 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Oct 2008 04:06:07 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 65187234C22A for ; Tue, 14 Oct 2008 21:06:44 -0700 (PDT) Message-ID: <597765954.1224043604410.JavaMail.jira@brutus> Date: Tue, 14 Oct 2008 21:06:44 -0700 (PDT) From: "Greg Wilkins (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-1650) Upgrade Jetty to 6.x MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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.