[
https://issues.apache.org/jira/browse/HADOOP-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Shvachko updated HADOOP-4618:
----------------------------------------
Resolution: Fixed
Release Note:
Changes to the public API:
- FSNamesystem.getNameNodeInfoPort() is removed.
- FSNamesystem.getDFSNameNodeMachine() and FSNamesystem.getDFSNameNodePort()
replaced by FSNamesystem.getDFSNameNodeAddress()
- Removed constructor NameNode(bindAddress, conf)
was:
Changes to the public API:
# FSNamesystem.getNameNodeInfoPort() is removed.
# FSNamesystem.getDFSNameNodeMachine() and FSNamesystem.getDFSNameNodePort()
replaced by FSNamesystem.getDFSNameNodeAddress()
# Removed constructor NameNode(bindAddress, conf)
Hadoop Flags: [Incompatible change, Reviewed] (was: [Incompatible change])
Status: Resolved (was: Patch Available)
I just committed this.
> Move http server from FSNamesystem into NameNode.
> -------------------------------------------------
>
> Key: HADOOP-4618
> URL: https://issues.apache.org/jira/browse/HADOOP-4618
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.1.0
> Reporter: Konstantin Shvachko
> Assignee: Konstantin Shvachko
> Fix For: 0.20.0
>
> Attachments: MoveHttpServer.patch, MoveHttpServer.patch,
> MoveHttpServer.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
