[ 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
