hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "eric baldeschwieler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-349) Allow info server to be turned off/on by conf file
Date Fri, 07 Jul 2006 17:35:30 GMT
    [ 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:
For more information on JIRA, see:

View raw message