[HADOOP-4618] Move http server from FSNamesystem into NameNode.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.1.0
• Fix Version/s: 0.20.0
• Hadoop Flags: Incompatible change, Reviewed

Release Note

Moved HTTP server from FSNameSystem to NameNode. Removed FSNamesystem.getNameNodeInfoPort(). Replaced FSNamesystem.getDFSNameNodeMachine() and FSNamesystem.getDFSNameNodePort() with new method FSNamesystem.getDFSNameNodeAddress(). Removed constructor NameNode(bindAddress, conf).

• Assignee: Konstantin Shvachko
• Reporter: Konstantin Shvachko
• Created: 07/Nov/08 22:20
• Updated: 08/Jul/09 16:43
• Resolved: 11/Nov/08 02:46

Description

NameNode is responsible now for starting its RPC server. The (web UI) http server is started inside FSNamesystem class.
I think it should be the NameNode's responsibility to deal with all issues intended for exposing information it holds to the outside world. This should include the RCP server as well as the http server.
And FSNamesystem class should be a logical container of internal namespace data-structures and in general should not be accessed directly from the outside.