Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <25801586.1152293730649.JavaMail.jira@brutus>
Date: Fri, 7 Jul 2006 17:35:30 +0000 (GMT+00:00)
From: "eric baldeschwieler (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-349) Allow info server to be turned
 off/on by conf file
In-Reply-To: <24802631.1152210629864.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HADOOP-349?page=comments#action_12419757 ] 

eric baldeschwieler commented on HADOOP-349:
--------------------------------------------

this is kind of pushing the opposite direction we're going.  We are adding more functionality to this server and since we want to have a multi-lingual interoperable protocol down the road, something over HTTP makes sense.  I'm imaging the HTTP server will eventually be the only port to reach these servers.

So a long term solution will need to allow you to use tomcat or run an embedded jeti on another port.  Not just turn of jetty.

> Allow info server to be turned off/on by conf file
> --------------------------------------------------
>
>          Key: HADOOP-349
>          URL: http://issues.apache.org/jira/browse/HADOOP-349
>      Project: Hadoop
>         Type: Improvement

>   Components: conf
>     Reporter: Barry Kaplan
>  Attachments: info_server_patch
>
> Since I am using hadoop within my own servlet which is not Jetty, it would be nice to not have to need Jetty to run my servlet. As such I propose adding an if statement/donf setting at FSNamesystem:171 as such         
> if(conf.getBoolean("dfs.info.active",true)){
>             this.infoPort = conf.getInt("dfs.info.port", 50070);
>             this.infoServer = new StatusHttpServer("dfs", infoPort, false);
>             this.infoServer.start();
> }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira