Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <19644554.1181590886296.JavaMail.jira@brutus>
Date: Mon, 11 Jun 2007 12:41:26 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1432) Use Grizzly for Fetching Map Output
 in Shuffle
In-Reply-To: <4970323.1180076841340.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Doug Cutting commented on HADOOP-1432:
--------------------------------------

bq. Some more experimentation needs to be done to make sure we are using the most appropriate Grizzly APIs (in terms of performance) before this patch can go in.

Yes.  In particular, as a performance optimization, it should show a significant speedup.

If it works well, we should ideally could convert all our Jetty daemons to Grizzly.  Grizzly supports the Servlet API, and we pre-compile all of our JSP pages to servlets, so that should be possible.

> Use Grizzly for Fetching Map Output in Shuffle
> ----------------------------------------------
>
>                 Key: HADOOP-1432
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1432
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Tahir Hashmi
>            Assignee: Tahir Hashmi
>         Attachments: 1432.patch, grizzly.tgz
>
>
> As mentioned in HADOOP-1273 and references therefrom, Jetty 6 still doesn't seem to be stable enough for use in Hadoop. Instead, we've decided to consider the usage of Grizzly Framework [https://grizzly.dev.java.net/] for NIO based communication.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.