FAQ
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


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

Search Discussions

  • Barry Kaplan (JIRA) at Jul 6, 2006 at 10:29 pm
    [ http://issues.apache.org/jira/browse/HADOOP-349?page=comments#action_12419609 ]

    Barry Kaplan commented on HADOOP-349:
    -------------------------------------

    Also see HADOOP-351
    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
    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
  • Barry Kaplan (JIRA) at Jul 7, 2006 at 5:15 pm
    [ http://issues.apache.org/jira/browse/HADOOP-349?page=all ]

    Barry Kaplan updated HADOOP-349:
    --------------------------------

    Attachment: info_server_patch

    adds config setting for turning off the info server
    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
  • eric baldeschwieler (JIRA) at Jul 7, 2006 at 5:37 pm
    [ 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
  • Doug Cutting (JIRA) at Jul 8, 2006 at 7:47 am
    [ http://issues.apache.org/jira/browse/HADOOP-349?page=comments#action_12419844 ]

    Doug Cutting commented on HADOOP-349:
    -------------------------------------

    What is the problem with running a Jetty-based daemon from within Tomcat?

    It sounds like you'd like to package daemons as war files. So, in this scheme, there would be separate namenode, datanode, tasktracker and jobtracker war file, since each exposes a distinct web interface, right? That's a larger change to Hadoop than simply disabling the jetty daemons, since Hadoop sometimes stores application state in the servlet context, etc.

    Short of that, you could simply package the datanode as a war file, but permit it to start its own daemon for it's web interface on a different port. Is that so horrible?
    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

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedJul 6, '06 at 6:32p
activeJul 8, '06 at 7:47a
posts5
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Doug Cutting (JIRA): 5 posts

People

Translate

site design / logo © 2022 Grokbase