Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <507443677.1231967459673.JavaMail.jira@brutus>
Date: Wed, 14 Jan 2009 13:10:59 -0800 (PST)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5023) Change hdfsproxy to use Tomcat
 instead of Jetty
In-Reply-To: <1688599713.1231872239980.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-5023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663886#action_12663886 ] 

Doug Cutting commented on HADOOP-5023:
--------------------------------------

> 1. The embedded feature of Jetty is not required as hdfsproxy is intended as a standalone server.

That's a reason Jetty isn't absolutely required, not a reason to use Tomcat.  And are you certain that we'd never want to bundle the hdfsproxy with some other daemon?

> 2. Tomcat has good production support at Yahoo, whereas Jetty doesn't.

Can you elaborate on what "good production support" means?

It seems reasonable to have an ant target that packages the hdfsproxy as a .war file that could be used in Tomcat.  Is more than that required to satisfy this?


> Change hdfsproxy to use Tomcat instead of Jetty
> -----------------------------------------------
>
>                 Key: HADOOP-5023
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5023
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: contrib/hdfsproxy
>            Reporter: Kan Zhang
>            Assignee: zhiyong zhang
>
> We plan to change hdfsproxy to use Tomcat instead of Jetty for the following reasons.
> 1. The embedded feature of Jetty is not required as hdfsproxy is intended as a standalone server.
> 2. Tomcat has good production support at Yahoo, whereas Jetty doesn't.

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